Network slice management

ABSTRACT

In a method for managing a physical network, whether a slice owner of a virtual network slice in the physical network is allowed to view a network information message is determined based on at least one of classification metadata or allocation metadata associated with the virtual network slice. The network information message, which is received from the physical network, includes at least one of (i) an autonomous notification from a network node in the physical network or (ii) operational data for the network node in the physical network. The network information message is provided to the slice owner in response to determining that the slice owner is allowed to view the network information message.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation-in-Part of International Application No. PCT/US2018/056706, filed Oct. 19, 2018, and of International Application No. PCT/US2018/056714, filed Oct. 19, 2018, each of which claims priority to provisional U.S. patent application No. 62/575,797, filed on Oct. 23, 2017, the entire contents of all of which are incorporated herein by reference.

BACKGROUND

Virtual network slicing (also referred to as network slicing or slicing) allows multiple logical or virtual networks to be created on top of a common shared physical network infrastructure.

SUMMARY

According to at least some example embodiments, notifications may be filtered more directly based on classification and/or allocation metadata, without the need to generate a network slice view. In at least one example embodiment, this may be achieved by relating a received notification to a corresponding entry in the classification metadata, and in turn, the allocation metadata. Thus, the metadata may be used directly to apply the filtering.

In one example, a corresponding entry in the classification metadata is found for a notification emanating from an “interface” instance. Once found, the “interface” and its key leaf may be identified in the Yang model of the device. The classification and allocation configurations may thus be applied to determine whether the notification should be visible in a virtual network slice. For example, if the “interface” key value is prefixed and the “interface” is classified as create-able in the classification metadata, then the notification may be filtered in and transformed (visible). If the key value is not prefixed, but appears as visible in the allocation metadata, then the notification may be filtered in and transformed. Otherwise, the notification is filtered out.

In some instances, the body of the notification may not contain enough information to relate the corresponding entity instance to an entry in the classification metadata. For example, if the classification metadata entry specifies an “interface” of type “channel group,” using a discriminator to narrow down the “interface” type as being “channel group,” then the body of the notification may not have enough information to relate the notification to an “interface” of type “channel group.” The notification may only specify an “interface” without specifying the type of “interface.” In this case, each classification metadata entry may be mapped to each related “interface” instance in the NETCONF datastore, and the mapping may be cached for efficiency.

Operational data may also be linked to network resources that may or may not be visible in a network slice. Thus, similar solutions to filter and transform operational data may be used to collect only the operational data that is visible in a given slice.

At least one example embodiment provides a method for managing a physical network, the method comprising: receiving a network information message from the physical network, the network information message including at least one of (i) an autonomous notification from a network node in the physical network or (ii) operational data for the network node in the physical network; determining whether a slice owner of a virtual network slice in the physical network is allowed to view the network information message based on at least one of classification metadata or allocation metadata associated with the virtual network slice; and providing the network information message to the slice owner in response to determining that the slice owner is allowed to view the network information message.

At least one other example embodiment provides a non-transitory computer readable storage medium storing computer executable instructions that, when executed at a network element, cause the network element to perform a method for managing a physical network, the method comprising: receiving a network information message from the physical network, the network information message including at least one of (i) an autonomous notification from a network node in the physical network or (ii) operational data for the network node in the physical network; determining whether a slice owner of a virtual network slice in the physical network is allowed to view the network information message based on at least one of classification metadata or allocation metadata associated with the virtual network slice; and providing the network information message to the slice owner in response to determining that the slice owner is allowed to view the network information message.

According to at least some example embodiments, the determining whether a slice owner of a virtual network slice in the physical network is allowed to view the network information message may include: identifying an entity instance at the network node having originated the network information message; identifying an entry for an entity type in the classification metadata based on the entity instance; and determining whether the slice owner is allowed to view the network information message based on the entry for an entity type in the classification metadata.

According to at least some example embodiments, the identifying an entry may identify the entry for an entity type in the classification metadata by matching schema details for the entity type with schema information for the entity instance.

The network information message may include a key value. The determining whether the slice owner is allowed to view the network information message may include: determining whether the entity type is classified as create-able for the virtual network slice in the classification metadata; determining whether the key value is prefixed with a prefix associated with the virtual network slice; and determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as create-able for the virtual network slice and whether the key value is prefixed with the prefix associated with the virtual network slice.

The determining whether the slice owner is allowed to view the network information message may include: determining whether the entity type is classified as allocate-able for the virtual network slice based on the entry for an entity type in the classification metadata; determining whether the entity instance is designated as visible in the virtual network slice based on the entry for an entity type in the classification metadata; and determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as allocate-able for the virtual network slice and whether the entity instance is designated as visible in the virtual network slice.

The determining whether the slice owner is allowed to view the network information message may include: determining whether the entity type is classified as within a notification scope of the virtual network slice based on the entry for an entity type in the classification metadata; and determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as within the notification scope of the virtual network slice.

The identifying an entry for an entity type in the classification metadata based on the entity instance may include: querying a mapping between network entities and entries in the classification metadata to identify the entry for an entity type in the classification metadata.

At least one other example embodiment provides a network element to manage a physical network, the network element comprising: means for receiving a network information message from the physical network, the network information message including at least one of (i) an autonomous notification from a network node in the physical network or (ii) operational data for the network node in the physical network; means for determining whether a slice owner of a virtual network slice in the physical network is allowed to view the network information message based on at least one of classification metadata or allocation metadata associated with the virtual network slice; and means for providing the network information message to the slice owner in response to determining that the slice owner is allowed to view the network information message.

According to at least some example embodiments, the means for determining whether a slice owner of a virtual network slice in the physical network is allowed to view the network information message may include: means for identifying an entity instance at the network node having originated the network information message; means for identifying an entry for an entity type in the classification metadata based on the entity instance; and means for determining whether the slice owner is allowed to view the network information message based on the entry for an entity type in the classification metadata.

According to at least some example embodiments, the means for identifying an entry for an entity type in the classification metadata may include means for matching schema details for the entity type with schema information for the entity instance.

The network information message may include a key value. The means for determining whether the slice owner is allowed to view the network information message may include: means for determining whether the entity type is classified as create-able for the virtual network slice in the classification metadata; means for determining whether the key value is prefixed with a prefix associated with the virtual network slice; and means for determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as create-able for the virtual network slice and whether the key value is prefixed with the prefix associated with the virtual network slice.

The means for determining whether the slice owner is allowed to view the network information message may include: means for determining whether the entity type is classified as allocate-able for the virtual network slice based on the entry for an entity type in the classification metadata; means for determining whether the entity instance is designated as visible in the virtual network slice based on the entry for an entity type in the classification metadata; and means for determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as allocate-able for the virtual network slice and whether the entity instance is designated as visible in the virtual network slice.

The means for determining whether the slice owner is allowed to view the network information message may include: means for determining whether the entity type is classified as within a notification scope of the virtual network slice based on the entry for an entity type in the classification metadata; and means for determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as within the notification scope of the virtual network slice.

The means for identifying an entry for an entity type in the classification metadata based on the entity instance may include means for querying a mapping between entity instances and entries in the classification metadata to identify the entry for an entity type in the classification metadata.

At least one other example embodiment provides a network element to manage a physical network, the network element comprising at least one processor and at least one memory. The at least one memory includes computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the network element to: receive a network information message from the physical network, the network information message including at least one of (i) an autonomous notification from a network node in the physical network or (ii) operational data for the network node in the physical network; determine whether a slice owner of a virtual network slice in the physical network is allowed to view the network information message based on at least one of classification metadata or allocation metadata associated with the virtual network slice; and provide the network information message to the slice owner in response to determining that the slice owner is allowed to view the network information message.

According to at least some example embodiments, the at least one memory and the computer program code may be further configured to, with the at least one processor, cause the network element to determine whether the slice owner of the virtual network slice in the physical network is allowed to view the network information message by: identifying an entity instance at the network node having originated the network information message; identifying an entry for an entity type in the classification metadata based on the entity instance; and determining whether the slice owner is allowed to view the network information message based on the entry for an entity type in the classification metadata.

The at least one memory and the computer program code may be further configured to, with the at least one processor, cause the network element to identify the entry for the entity type in the classification metadata by matching schema details for the entity type with schema information for the entity instance.

The network information message may include a key value. The at least one memory and the computer program code may be further configured to, with the at least one processor, cause the network element to determine whether the slice owner is allowed to view the network information message by: determining whether the entity type is classified as create-able for the virtual network slice in the classification metadata; determining whether the key value is prefixed with a prefix associated with the virtual network slice; and determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as create-able for the virtual network slice and whether the key value is prefixed with the prefix associated with the virtual network slice.

The at least one memory and the computer program code may be further configured to, with the at least one processor, cause the network element to determine whether the slice owner is allowed to view the network information message by: determining whether the entity type is classified as allocate-able for the virtual network slice based on the entry for an entity type in the classification metadata; determining whether the entity instance is designated as visible in the virtual network slice based on the entry for an entity type in the classification metadata; and determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as allocate-able for the virtual network slice and whether the entity instance is designated as visible in the virtual network slice.

The at least one memory and the computer program code may be further configured to, with the at least one processor, cause the network element to identify the entry for the entity type in the classification metadata based on the entity instance by querying a mapping between entity instances and entries in the classification metadata to identify the entry for an entity type in the classification metadata.

BRIEF DESCRIPTION OF THE DRAWINGS

Example embodiments will become more fully understood from the detailed description given herein below and the accompanying drawings, wherein like elements are represented by like reference numerals, which are given by way of illustration only and thus are not limiting of this disclosure.

FIG. 1 is a block diagram illustrating a physical network architecture including a plurality of virtual network slices and a network management virtualizer, according to one or more example embodiments.

FIG. 2 is an embedded flow diagram illustrating a method according to one or more example embodiments.

FIG. 3 is an embedded flow diagram illustrating another method according to one or more example embodiments.

FIG. 4 illustrates an example data model for a passive optical network (PON) virtual network slice.

FIG. 5 is an embedded flow diagram illustrating a method according to one or more example embodiments.

FIG. 6 is an embedded flow diagram illustrating a method according to one or more example embodiments.

FIG. 7A is an embedded flow diagram illustrating a method according to one or more example embodiments.

FIG. 7B is a flow chart illustrating a method according to one or more example embodiments.

FIG. 7C is a flow chart illustrating a method according to one or more example embodiments.

FIG. 7D is a flow chart illustrating a method according to one or more example embodiments.

FIG. 8 is an embedded flow diagram illustrating a method according to one or more example embodiments.

FIG. 9A is an embedded flow diagram illustrating a method according to one or more example embodiments.

FIG. 9B is a flow chart illustrating a method according to one or more example embodiments.

FIG. 9C is a flow chart illustrating a method according to one or more example embodiments.

FIG. 9D is a flow chart illustrating a method according to one or more example embodiments.

FIG. 9E is a flow chart illustrating a method according to one or more example embodiments.

FIG. 10 is a flow diagram illustrating a method according to one or more example embodiments.

FIG. 11 is a flow chart illustrating a method according to one or more example embodiments.

FIG. 12A is a flowchart illustrating a method according to one or more example embodiments.

FIG. 12B is a flowchart illustrating a method according to one or more example embodiments.

FIG. 13 is an embedded flow diagram illustrating a method according to one or more example embodiments.

FIG. 14 is an embedded flow diagram illustrating a method according to one or more example embodiments.

FIG. 15 illustrates classification metadata according to one or more example embodiments.

FIG. 16 illustrates allocation metadata according to one or more example embodiments.

FIG. 17 is a flow chart illustrating a method according to one or more example embodiments.

FIG. 18 is a flow chart illustrating a method according to one or more example embodiments.

FIG. 19 provides a general architecture and functionality suitable for implementing functional elements described herein or portions of functional elements described herein.

FIG. 20 is an embedded flow diagram illustrating a method according to one or more example embodiments.

FIG. 21 is an embedded flow diagram illustrating a method according to one or more example embodiments.

FIG. 22 is a flow chart illustrating a method according to one or more example embodiments.

FIG. 23 is a flow chart illustrating a method according to one or more example embodiments.

FIG. 24 is a flow chart illustrating a method according to one or more example embodiments.

FIG. 25 is a flow chart illustrating a method according to one or more example embodiments.

FIG. 26 illustrates classification metadata according to one or more example embodiments.

It should be noted that these figures are intended to illustrate the general characteristics of methods, structure and/or materials utilized in certain example embodiments and to supplement the written description provided below. These drawings are not, however, to scale and may not precisely reflect the precise structural or performance characteristics of any given embodiment, and should not be interpreted as defining or limiting the range of values or properties encompassed by example embodiments. The use of similar or identical reference numbers in the various drawings is intended to indicate the presence of a similar or identical element or feature.

DETAILED DESCRIPTION

Various example embodiments will now be described more fully with reference to the accompanying drawings in which some example embodiments are shown.

Detailed illustrative embodiments are disclosed herein. However, specific structural and functional details disclosed herein are merely representative for purposes of describing example embodiments. The example embodiments may, however, be embodied in many alternate forms and should not be construed as limited to only the embodiments set forth herein.

Accordingly, while example embodiments are capable of various modifications and alternative forms, the embodiments are shown by way of example in the drawings and will be described herein in detail. It should be understood, however, that there is no intent to limit example embodiments to the particular forms disclosed. On the contrary, example embodiments are to cover all modifications, equivalents, and alternatives falling within the scope of this disclosure. Like numbers refer to like elements throughout the description of the figures.

Example embodiments will be discussed with regard to a NETCONF-managed network. However, it should be understood that example embodiments may also be applicable to other networks, such as Simple Network Management Protocol (SNMP)-managed networks and the like. The NETCONF protocol is defined in RFC 6241 and SNMP is defined in RFC 1066. These protocols define mechanisms through which network devices may be managed, configuration data information can be retrieved, and new configuration data can be uploaded and manipulated.

FIG. 1 is a simplified block diagram illustrating a physical network architecture including a plurality of virtual network slices and a network management virtualizer, according to one or more example embodiments.

Referring to FIG. 1, the physical network architecture (also referred to as a physical network infrastructure or physical network) is an example of a shared physical network on top of which a plurality of virtual network slices S-1 through S-N are created. Each virtual network slice S-1 through S-N corresponds to a virtual network and a set of virtual network devices assigned to the virtual network.

The physical network architecture includes a plurality of network nodes 104-1, 104-2, 104-3, 104-4, . . . , 104-M, which are connected to a core network 106. In the example shown in FIG. 1, the set of virtual network devices assigned to virtual network slice S-1 includes nodes 104-1 and 104-3 and the set of virtual network devices assigned to the virtual network slice S-N includes nodes 104-1, 104-2 and 104-4. Although discussed herein with regard to nodes, the set of virtual devices may include network nodes, entity instances within network nodes, and the like, which are in communication with the core network 106.

The example embodiment shown in FIG. 1 represents a tree network topology, and example embodiments will be discussed herein with regard to the tree network topology for example purposes. It should be understood, however, that example embodiments may be applicable to other network topologies (e.g., ring, mesh, star, fully connected, line, bus, etc.) and/or other device types; that is, for example, example embodiments may be applicable to networks irrespective of network topology or device type.

Each respective virtual network slice S-1 through S-N is accessible and managed by a respective slice owner 110-S-1 through 110-S-N. Each slice owner 110-S-1 through 110-S-N has access to only their respective virtual network slice. An example of a slice owner is a virtual network operator (VNO) for a network provider, which utilizes the physical network infrastructure of another network provider. By contrast, the entire physical network, including all virtual network slices, is accessible and managed by a slice manager 110. The slice manager 110 acts as a “super user,” which is able to configure any and all aspects of the physical network. In a more specific example, the slice manager 110 may be similar to a super user in the UNIX platform.

According to one or more example embodiments discussed herein, the slice owners 110-S-1 through 110-S-N and the physical network devices may be slicing unaware, such that a slice owner sees only a slice subset of the network physical resources and is unaware of the virtual network slicing. Although example embodiments will be discussed herein with regard to slicing unaware slice owners and physical network devices, it should be understood that example embodiments may be applicable to scenarios in which the physical network devices and/or one or more slice owners are slicing aware.

Still referring to FIG. 1, the physical network architecture further includes a network management virtualizer 100, which includes a physical network datastore 1020. The network management virtualizer 100 may be implemented on a hardware computing platform at, for example, a network management entity. The hardware computing platform may be built around multiple server boards utilizing processing circuitry (e.g., one or more processors or processing cores).

According to one or more example embodiments, the network management virtualizer 100 and/or the physical network datastore 1020 may be located at a network management entity, which may be located at central office (CO) or distributed in the cloud via a cloud architecture. For a NETCONF-managed network, the physical network datastore 1020 stores network configuration for the physical network infrastructure. The physical network datastore 1020 may be stored in a memory at a network management entity.

In one example, a network management entity may be a network management server that is separate from network devices, and that may connect and manage multiple networks or network devices remotely. Alternatively, the network management entity may be distributed among multiple different network management servers in a cloud architecture.

According to one or more example embodiments, virtual network slicing discussed herein may transcend the architecture of the network virtualizer (or entity in which slicing is implemented), including where containers, virtual machines, or bare metal is used, as well as aspects of the run-time environment. If implemented in the cloud, example embodiments may or may not be distributed (e.g., example embodiments may be in the cloud and may be distributed or centralized).

In the example shown in FIG. 1, the physical network datastore 1020 is a NETCONF datastore storing network configuration information as encoded eXtensible Markup Language (XML) documents and files. However, an equivalent datastore for SNMP network devices is referred to as a Management Information Base (MIB).

Example embodiments are discussed herein with regard to pairing XML encoding with XML Stylesheet Language for Transformations (XSLT) and XQuery. It should be understood, however, that example embodiments should not be limited to this example. Rather, any transformation technology with respect to any encoding (e.g., comparable to XSLT with respect to XML encoding) may be used.

The network management virtualizer 100 may enable virtual network slicing from a single physical network datastore, residing in the management layer, without duplicating data across multiple physical network datastores on a slice-by-slice basis. The single physical network datastore may store network configuration information for the entire physical network and may be used for Persistence Management Agent Aggregation (PMAA); that is, offline provisioning across all network devices.

Still referring to FIG. 1, the network management virtualizer 100 is in communication with each of the nodes 104-1 through 104-M in the physical network. At the direction of slice owners 110-S-1 through 110-S-N or the slice manager 110, the network management virtualizer 100 implements configuration and management of the virtual network slices S-1 through S-N, and virtual network devices assigned thereto, within the physical network.

Network configuration for a physical network infrastructure depends on the models used to configure individual devices in the physical network as well as the model used to configure the network manager managing the physical network. In the case of NETCONF, network models are typically defined in YANG. YANG is a data modelling language used to model configuration and state data manipulated by NETCONF, NETCONF remote procedure calls (RPCs), and NETCONF notifications. YANG is defined in RFC 6020. Given the tree nature of YANG models, individual network entities can be leaves and sets thereof can be subtrees.

As mentioned above, example embodiments will be discussed herein with regard to a NETCONF-managed network. In this regard, example embodiments will be discussed with regard to NETCONF, a NETCONF model and the YANG model.

Although access networks may lend themselves to devices aligned with standard YANG models (e.g., Broadband Forum (BBF) WT-385), example embodiments should not be limited to this example. Rather, example embodiments may transcend the use of any device YANG model and/or any network type.

An “entity type” is a NETCONF model entry that represents a network “resource” residing in either the network manager or a network device. A network resource is considered configured once an “entity instance” corresponding to the network “resource” (entity type) has been created in the physical network datastore 1020, and the entity attributes are then populated as needed. An “entity type” is the definition of the entity in the model.

An “entity instance” or “network entity instance” is an embodiment of the “entity type” once the entity type has been instantiated and inserted as a distinct entry into the physical network datastore 1020.

One or more example embodiments also provide methods to define, configure and manage virtual network slices by utilizing classification of network configuration models and run-time allocation and/or assignment of entity instances to virtual network slices.

Classification of network configuration models allows for defining of boundaries within the models of what entity types are visible and modifiable by a slice owner in a virtual network slice. Different entity types in the models are classified based on their configurability in a virtual network slice, and network entities may be assigned to a virtual network slice according to their classification.

Individual entities or sets thereof may be uniquely identifiable using keys indicative of the corresponding network models.

Run-time allocation and/or assignment of entity instances to virtual network slices refers to the addition of slicing configuration (on top of classification) based on network provisioning data instantiated into a database (e.g., at the physical network datastore) at run-time. This virtual network slice configuration points to specific instances of network provisioning artifacts in the database, and may be specified only after network provisioning is persisted into a database at run-time. A slice manager may explicitly assign entity instances to a given virtual network slice. In addition, the slice manager may specify whether the entity instances are read-only or read-write accessible.

In a NETCONF-managed network, such as that shown in FIG. 1, virtual network slicing may be implemented using XSLT. An XSLT transformation is typically expressed as a file with the “.xslt” extension and encoded in XML. An XSLT transformation may be formulated programmatically, for example, within a computer program (e.g., a Java program) at run-time. Similarly, the transformation may be applied to an XML-encoded message or datastore at run-time. At least one example embodiment may utilize a javax.xml.transform package, and any Java Run-time Environment (JRE) that implements javax.xml.transform may be used. In the case of at least one example embodiment, OpenJDK 8 may be used.

FIG. 2 is an embedded flow diagram illustrating a method for providing virtual network slice views of the physical network datastore 1020 to slice owners of the plurality of virtual network slices S-1 through S-N in FIG. 1, according to one or more example embodiments. A virtual network slice view may also be referred to as a datastore virtual view.

The virtual network slice view for a virtual network slice is the virtual network slice view of the physical network datastore projected to the slice owner. The virtual network slice view may also be in the form of a user interface (e.g., graphical user interview (GUI)) that allows the slice owner (or owners) to view the entities, entity types, entity instances and configuration information assigned to the virtual network slice (or slices). In one example, the slice owner may access the virtual network slice view via a remote terminal. The virtual network slice view may be provided to the remote terminal by the network management virtualizer 100.

Referring to FIG. 2, XSLT transformations are applied to messages (e.g., NETCONF messages) to and from the network management virtualizer 100. The XSLT transformations filter or transform the messages such that the virtual network slice view provides only information that a particular slice owner is allowed to view.

According to at least one example embodiment, transformations may be optimized and cached for application to subsequent messages. A cached and optimized transformation may need to be replaced when either the related classification or allocation metadata is changed.

In this example, network configuration information is encoded in XML and stored in the physical network datastore 1020. Because the physical network datastore 1020 is encoded in XML, a single physical network datastore may be maintained for the entire physical network and the XML of the physical network datastore may be transformed based on a request from a slice owner for a given network slice to provide only network configuration information for the given network slice to the requesting slice owner. By transforming the physical network datastore XML on a per-request basis, a network slice view of the network may be provided to a slice owner without maintaining a separate physical network datastore for each virtual network slice. Accordingly, overhead and memory required to maintain and reconcile redundant data across multiple slices as well as the physical network data may be reduced.

According to one or more example embodiments, virtual network slicing may be implemented using unique tags, each of which uniquely identifies a virtual network slice. Within the physical network datastore 1020, physical data associated with a given virtual network slice is identified using the unique tag.

Tagging may be implemented in any manner depending on the nature of the physical network datastore and data encoding. As an example, in the NETCONF-managed network shown in FIG. 1, in which the physical network datastore 1020 is encoded in XML, unique tags may be implemented using prefixing or suffixing with data key values. A special character may be used to separate the prefix or suffix from the original key value.

FIG. 3 is an embedded flow diagram illustrating a method for implementing tagging (also referred to as pre-fixing) for virtual network slices S-1 through S-N, according to one or more example embodiments.

Referring to FIG. 3, the special character “-” is used as a separator such that a key tag for virtual network slice S-1 is ‘Slice1tag˜keyX’, where the tag is ‘Slice1tag’ and the key is ‘keyX’. In another example, a key tag for virtual network slice S-N is ‘SliceNtag˜keyZ’, where the tag is ‘SliceNtag’ and the key is ‘keyZ’. The network management virtualizer 100 may utilize XSLT transformations to filter or transform information from the physical network datastore 1020 to generate the virtual network slice view for the respective virtual network slices.

Key tags may be used to link network entities to a virtual network slice in the physical network datastore 1020. This enables the network management virtualizer 100 to differentiate between network entities created by a slice owner and the slice manager. This also distinguishes entities created by different slice owners.

Referring back to FIG. 1, because the physical network datastore 1020 and messages in the NETCONF-managed network shown in FIG. 1 are encoded in XML, the XML document of the single physical network datastore 1020 may be transformed based on a request from a slice owner such that a virtual network slice view of the physical network for only the virtual network slice managed by the requesting slice owner is provided without maintaining a separate physical network datastore for the individual virtual network slice. As mentioned above, this may suppress overhead or memory required to maintain or reconcile redundant data across multiple slices as well as the physical network data. Example embodiments may be applicable to any virtual network slicing of any NETCONF-managed network, as well as other network management protocols, datastore encoding and message encoding.

According to at least one example embodiment, the network management virtualizer 100 uses XSLT to filter access to the physical network datastore 1020 by a slice owner, thereby projecting a slice view of the physical network datastore to the slice owner, wherein the slice view includes only information associated with the virtual network slice associated with the slice owner. Thus, the slice view of the physical network datastore 1020 includes only a portion of the information stored in the physical network datastore 1020.

According to at least some example embodiments, the network management virtualizer 100 uses XSLT to transform and filter XML-encoded NETCONF requests from slice owners 110-S-1 through 110-S-N of virtual network slices S-1 through S-N, and to transform and filter XML-encoded network configuration information provided to the slice owners 110-S-1 through 110-S-N for virtual network slices S-1 through S-N.

According to at least one example embodiment, slice views may be defined at least in part by metadata for explicit allocation of network entity instances to each virtual network slice at runtime. Slice views may also be defined at least in part by metadata for the classification of entity types in the network model (e.g., YANG) for the physical network architecture.

According to at least one example embodiment, boundaries within the models of what is visible and modifiable by a slice owner in a virtual network slice may be defined utilizing metadata to classify entity types. In this regard, different entity types in the models may be classified based on their configurability in a given virtual network slice, and entity instances may be assigned to a virtual network slice according to their classification.

In one example, entity types may be classified as: visible, access-configurable, and create-able.

The visible classification denotes an entity type that is visible to the slice owner.

The access-configurable (or allocate-able) classification denotes an entity type that is read or read-write accessible by the slice owner. An entity type classified as access-configurable cannot be created by the slice owner, but the attributes of the entity type may be modified by the slice owner if read-write accessible. In this example, corresponding entity instances may also be created and assigned to a virtual network slice at run-time by the slice manager 110.

An entity type classified as create-able may be created by the slice owner. These entity types may be distinguished from entity types created by the slice manager 110 in the physical network datastore 1020 using tagging, which will be discussed in more detail later. In this example, corresponding entity instances may also be created and assigned to a virtual network slice at run-time by a slice owner or the slice manager 110.

Still referring to FIG. 1, the physical network datastore 1020 may store network configuration information for network entities. The network configuration information may include network entity classification metadata stored as a classification entry in the physical network datastore 1020. The network entity classification metadata may include: i) a unique identifier; and ii) model schema details required to identify the network entity or sets thereof in the network models including key definitions. In one example, model schema details refer to how the metadata expressions identify artifacts in the network management models (e.g., YANG). In this case, schema is used in a fashion similar to database schema, but referring to a device model artifact expressed in, for example, YANG for NETCONF or in a MIB for SNMP. Entity classification metadata will be discussed in more detail later with regard to FIG. 15.

Returning to FIG. 1, the slice manager 110 may explicitly assign instances of entity types (entity instances) to a given virtual network slice among the virtual network slices S-1 through S-N. In addition, the slice manager 110 may specify whether the entity instances are read-only or read-write accessible and/or specify limits (e.g., maximum number of entity instances) per virtual network slice. Metadata indicative of whether the entity instance is read-only or read-write accessible and limits per virtual network slice may be stored as part of the allocation metadata in the physical network datastore 1020.

The allocation metadata may also be part of the network configuration information, and may be stored in an allocation (or assignment) entry in the physical network datastore 1020. In one example, an allocation entry may include: i) the virtual network slice; ii) a unique identifier matching the classification entry being referred to; iii) a set of unique keys identifying the network entity instances in the allocation metadata; and iv) accessibility information (e.g., read-only or read-write) for the allocation metadata. Allocation metadata will be discussed in more detail later with regard to FIG. 16.

As mentioned above, one or more example embodiments may implement virtual network slicing using unique tags, wherein each unique tag uniquely identifies a virtual network slice. According to one or more example embodiments, network information (e.g., configuration information) for devices allocated to a given virtual network slice is identified using a key tag that is unique to the virtual network slice.

FIG. 4 illustrates an example data model for a passive optical network (PON) virtual network slice.

Referring to FIG. 4, each virtual network slice includes instances: Optical Line Terminal (OLT) 402, PON Port 404, Optical Network Terminal (ONT) 406, ONT Port 408, Layer 2 End Points 410, Layer 2 Bridge 412, and Network Port 414.

In this example, the data model includes an entity instance OLT 402, an entity instance Network Port 414, and four entity instances P1, P2, P3 and P4 for the PON Port Type.

Tables 1.1, 1.2 and 1.3 shown below illustrate a first configuration of the virtual network slice for slice owners blue and green of a virtual network slice.

TABLE 1.1 Slice access Slice access Entity configuration for configuration for instances Slicing model slice owner ‘blue’ slice owner ‘green’ Network access Allocate- Read accessible Read accessible Port 414 able PON Port access Allocate-able Read accessible Read accessible P1, P2, P3, P4

TABLE 1.2 Datastore entries Entity Type for slice owner Datastore entries for Identifier Slicing model ‘blue’ slice owner ‘green’ ONT Type ID Create-able by slice ONT blue ~406 ONT green ~406 owners ONT Port Type ID Create-able by slice ONT Port blue ~408 ONT Port green ~408 owners Layer 2 Bridge Type Create-able by slice Layer 2 Bridge Layer 2 Bridge green ~412 ID owners blue ~412 Layer 2 End Point Create-able by slice Layer 2 End Point Layer 2 End Point Type ID owners blue ~410 green ~410

TABLE 1.3 Entity Slice partition Slice partition Type configuration for configuration for Identifier Slicing model slice owner ‘blue’ slice owner ‘green’ ONT Type Create-able by slice Limited to 100 Limited to 200 ID owners ONT Port Create-able by slice Unlimited Unlimited Type ID owners Layer 2 Create-able by slice Limited to 2 Limited to 4 Bridge owners Type ID Layer 2 Create-able by slice Unlimited Unlimited End Point owners Type ID

As shown in Table 1.1, instances Network Port 414 and PON Port 404 are read-only (viewable) to each slice owner. As show in Table 1.3, instances of the ONT Type, ONT Port Type, Layer 2 Bridge Type and Layer 2 End Points Type are each create-able by slice owners blue and green. However, instances of the ONT Type are limited to 100 instances for the slice owner blue and limited to 200 instances for slice owner green; instances of the Layer 2 Bridge Type are limited to two for the slice owner blue and limited to four instances for the slice owner green. Instances of the ONT Port Type and the Layer 2 End Points Type are unlimited for each of slice owners blue and green. Table 1.2 shows datastore entries for each slice owner.

Table 2 shown below illustrates a second configuration of the virtual network slice for slice owners blue and green of the virtual network slice.

TABLE 2 Slice access Slice access configuration configuration for for slice Entity instances Slicing model slice owner ‘blue’ owner ‘green’ Network Port 414 access Allocate- Read accessible Read accessible able PON Port P1, P2 access Allocate- Read and write able accessible PON Port P3, P4 access Allocate- Read and write able accessible

As shown in Table 2 , instance Network Port 414 is read-only to each, whereas specific instances of the PON Port Type are readable-writeable by respective slice owners. For example, the instances P1 and P2 of the PON Port Type are readable-writeable by the slice owner blue, whereas instances P3 and P4 of the PON Port Type are readable-writeable by the slice owner green.

Example operation of the network management virtualizer 100 will be described in more detail below. As mentioned above, for example purposes, the example operation will be discussed with regard to the NETCONF-managed network shown in FIG. 1. However, example embodiments should not be limited to this example.

FIGS. 5-7A are flow diagrams illustrating methods for providing network configuration and/or operational information in response to a query (or query message) from a slice owner and a slice manager, according to one or more example embodiments.

In FIGS. 5-7A, the flow diagrams are embedded in a portion of the physical network architecture shown in FIG. 1. As shown, the portion of the physical network architecture includes the slice owner 110-S-1, virtual network slice S-1, the slice manager 110, network management virtualizer 100 and the physical network datastore 1020. FIGS. 5-7A also illustrate the filtering interface between the network slice view seen by the slice owner 110-S-1 and the physical network view seen by the slice manager 110. FIGS. 5-7A will be discussed with regard to the NETCONF “GET” Remote Procedure Call (RPC). However, it should be understood that example embodiments are not limited to this example, but rather example embodiments are applicable to other NETCONF RPCs, such as the “GET-CONFIG” RPC.

Referring to FIG. 5, the slice owner 110-S-1 may request operational information for the physical network through the slice view by issuing a NETCONF GET RPC (500) to the network management virtualizer 100. The GET RPC may also be referred to as a query, query message or query filter.

The network management virtualizer 100 filters the GET RPC for the slice owner 110-S-1. The slice owner 110-S-1 may specify a filter that drives the content of the response output by the network management virtualizer 100 in response to the query. The network management virtualizer 100 filters or transforms (e.g., by applying XSLT transforms) the query from the virtual network slice view to the physical network view.

FIG. 6 illustrates a portion of the embedded flow diagram shown in FIG. 5 in more detail.

Referring to FIG. 6, the GET RPC may be XSLT-transformed by adding key value tags based on classification and allocation metadata for the virtual network slice S-1. Allocation metadata may have priority in the sense that a network entity having associated metadata indicating that the network entity was created by the slice manager 110 and made visible in the virtual network slice S-1 is not tagged. Alternatively, if the classification metadata indicates that the network entity is classified as create-able within the virtual network slice S-1, then the network entity is tagged.

In the example shown in FIG. 6, the network management virtualizer 100 applies XSLT classification and allocation tagging to the GET RPC from the slice owner 110-S-1.

Returning to FIG. 5, in response to the GET RPC from the slice owner 110-S-1, the network management virtualizer 100 issues a GET RPC (508) to the devices in the network to obtain operational information for the network devices allocated to the virtual network slice S-1. In response to the GET RPC (508), the devices in the network provide operational information to the network management virtualizer 100 (510).

The network management virtualizer 100 then generates a NETCONF RESPONSE (502) to the slice owner 110-S-1. The RESPONSE may include a response data tree. The network management virtualizer 100 filters or transforms (e.g., XSLT-transforms) the RESPONSE from the physical network view to the virtual network slice view provided to the slice owner 110-S-1 and outputs the RESPONSE to the slice owner 110-S-1.

Still referring to FIG. 5, to request network configuration information for devices assigned to the virtual network slice S-1, the slice owner 110-S-1 may request network configuration information from the physical network datastore 1020 at the network management virtualizer 100 through the slice view by issuing a “GET-CONFIG” RPC to the network management virtualizer 100.

The “GET-CONFIG” RPC is filtered in the same or substantially the same manner as the GET RPC for the slice owner 110-S-1.

In response to the GET-CONFIG RPC from the slice owner 110-S-1, the network management virtualizer 100 obtains the network configuration information from the physical network datastore 1020 and generates a RESPONSE including the requested network configuration information. The network management virtualizer 100 filters or transforms the RESPONSE from the physical network view to provide the slice view to the slice owner 110-S-1 in the same or substantially the same manner as the GET RPC. Example filtering of the RESPONSE will be discussed in more detail below with regard to FIG. 7A.

FIG. 7A illustrates a portion of the embedded flow diagram shown in FIG. 5 in more detail. In the example embodiment shown in FIG. 7A, the network management virtualizer 100 XSLT-transforms the RESPONSE using an XML pipeline of three XSLT transformations. As mentioned above, the RESPONSE may include a response data tree. The example embodiment shown in FIG. 7A will be described with regard to a response data tree for example purposes.

As shown in FIG. 7A, the response data tree is first pruned according to the entity type classification metadata (XSLT classification pruning). The response data tree is then pruned according to the entity instance allocation metadata (XSLT allocation tagging). The virtual network slice tags are then processed by being removed from the entity key values that are tagged (XSLT tag processing). The transformed RESPONSE is then provided to the slice owner 110-S-1. Example embodiments of XSLT classification pruning, XSLT allocation tagging and XSLT tag processing will be discussed in more detail below with regard to FIGS. 7B-7D.

The slice manager 110 may issue queries (e.g., GET or GET-CONFIG RPCs) to, and receive query responses (e.g., RESPONSEs) from, the network management virtualizer 100 in the same or substantially the same manner as the slice owner 110-S-1. However, the queries from, and query responses to, the slice manager 110 need not be filtered or transformed as discussed above with regard to the slice owner 110-S-1.

FIG. 7B is a flow chart illustrating a method for XSLT classification pruning according to one or more example embodiments. In describing the example embodiment shown in FIG. 7B, the RESPONSE message will be referred to more generically as a query response or query response message.

Referring to FIG. 7B, at step S700B the network management virtualizer 100 reads a next entity type (the current entity type) from a list of visible network entity types in the classification metadata for the virtual network slice S-1 stored at the physical network datastore 1020.

At step S702B, the network management virtualizer 100 uses schema details for the current entity type in the classification metadata to formulate an XSLT expression to prune the corresponding visible XML subtree(s) in the query response message. As mentioned above, schema details refer to how the metadata expressions identify artifacts in the network management models (e.g., YANG).

At step S704B, the network management virtualizer 100 adds the XSLT expression to the XSLT transformation so that the visible XML subtree(s) corresponding to the current entity type are kept, and the rest are discarded, when the XSLT transformation is applied to the query response message.

At step S706B, the network management virtualizer 100 determines whether the current entity type is the last entity type in the list of visible entity types.

If the current entity type is not the last entity type in the list of visible entity types, then the process returns to step S700B and continues as discussed herein for the next entity type in the list of visible entity types in the classification metadata for the virtual network slice S-1.

Returning to step S706B, if the current entity type is the last entity type in the list of visible entity types in the virtual network slice S-1, then the network management virtualizer 100 applies the XSLT transformation to the query response message at step S708B.

At step S710B, the network management virtualizer 100 then forwards transformed query response message for XSLT allocation tagging.

FIG. 7C is a flow chart illustrating a method for XSLT allocation tagging according to one or more example embodiments. In describing the example embodiment shown in FIG. 7C, the RESPONSE message will again be referred to more generically as a query response or query response message.

Referring to FIG. 7C, at step S700C the network management virtualizer 100 reads a next entity type (current entity type) from the list of allocate-able and create-able entity types in the classification metadata for the virtual network slice S-1.

According to at least one example embodiment, the list of allocate-able and create-able entity types is a merged list including slice entity types in a deviceSlicingAccessConfigurables list and slice entity types in a deviceSlicingCreate-ables list. The deviceSlicingAccessConfigurables list includes slice entity types created by the slice manager 110 and shared among the slice owners 110-S-1 through 110-S-N. The deviceSlicingCreate-ables list includes a list of slice entity types created by the slice owners 110-S-1 through 110-S-N or created by the slice manager 110 and shared among slice owners 110-S-1 through 110-S-N. According to at least one example embodiment, the same entity type may not show up in both the deviceSlicingCreate-ables list and the deviceSlicingAccessConfigurables list.

At step S702C, the network management virtualizer 100 queries the allocation metadata for corresponding instances of the current entity type from the physical network datastore 1020 based on the slice entity type identifier for the current entity type in the classification metadata.

If the network management virtualizer 100 finds instances of the current entity type in the allocation metadata, then at step S714C the network management virtualizer 100 formulates an XSLT expression to tag the corresponding visible XML subtrees in the query response message based on the keys for the instances of the current entity type found at step S704C.

At step S712C, the network management virtualizer 100 adds the XSLT expression to the XSLT transformation to tag the visible XML subtrees when the XSLT transformation is applied to the query response message.

The network management virtualizer 100 then determines whether the current entity type is the last entity type in the list of allocate-able and create-able entity types at step S706C.

If the network management virtualizer 100 determines that the current entity type is not the last entity type in the list of allocate-able and create-able entity types at step S706C, then the process returns to step S700C and continues as discussed herein for the next entity type in the list of allocate-able and create-able entity types.

Returning to step S706C, if the network management virtualizer 100 determines that the current entity type is the last entity type in the list of allocate-able and create-able entity types, then at step S708C the network management virtualizer 100 applies the XSLT transformation to the response query message. At step S710C, the network management virtualizer 100 then forwards the transformed response query message for further processing.

Returning to step S704C, if the network management virtualizer 100 does not find corresponding instance of the current entity type in the allocation metadata, the process then proceeds to step S706C and continues as discussed above.

FIG. 7D is a flow chart illustrating a method for XSLT tag processing, according to one or more example embodiments. In describing the example embodiment shown in FIG. 7D, the RESPONSE message will again be referred to more generically as a query response or query response message.

Referring to FIG. 7D, similar to step S700C in FIG. 7C, at step S700D the network management virtualizer 100 again reads the next entity type from the list of allocate-able and create-able entity types in the classification metadata for the virtual network slice S-1.

At step S702D, the network management virtualizer 100 formulates an XSLT expression to remove untagged entities from the query response message based on the schema details for the current entity type in the classification metadata.

At step S704D, the network management virtualizer 100 adds the XSLT expression to the XSLT transformation so that untagged entities are discarded from the query response message when the XSLT transformation is applied to the query response message.

At step S706D, the network management virtualizer 100 formulates another XSLT expression to subsequently remove tags from key values for the tagged entities based on the schema details for the current entity type in the classification metadata.

At step S708D, the network management virtualizer 100 adds the XSLT expression formulated at 5706D to the XSLT transformation to remove the tags added in accordance with the XSLT allocation tagging discussed above with regard to FIG. 7C when the XSLT transformation is applied to the query response message.

At step S710D, the network management virtualizer 100 determines whether the current entity type is the last entity type in the list of allocate-able and create-able entity types.

If the current entity type is not the last entity type in the list of allocate-able and create-able entity types, then the process returns to step S700D and the network management virtualizer 100 performs another iteration of the process for the next entity type in the list of allocate-able and create-able entity types.

Returning to step S710D, if the current entity type is the last entity type in the list of allocate-able and create-able entity types, then the network management virtualizer 100 applies the XSLT transformation to the query response message at step S712D, and forwards the transformed query response message to the slice owner 110-S-1 at step S714D. In forwarding the transformed query response message to the slice owner 110-S-1, the network management virtualizer 100 provides only information associated with the virtual network slice S-1 to the slice owner 110-S-1 without the need to replicate data across multiple physical network datastores for multiple virtual network slices.

FIGS. 8 and 9A are flow diagrams illustrating methods for configuring a virtual network slice according to one or more example embodiments.

In the FIGS. 8 and 9A, the flow diagrams are embedded in a portion of the physical network architecture of FIG. 1 including the slice owner 110-S-1 of virtual network slice S-1, the slice manager 110, the network management virtualizer 100 and the physical network datastore 1020. FIGS. 8 and 9A also illustrate the filtering interface between the virtual network slice view seen by the slice owner 110-S-1 and the physical network view seen by the slice manager 110.

The slice owner 110-S-1 or the slice manager 110 may configure the virtual network slice S-1 using an EDIT-CONFIG RPC. As shown in FIG. 8, the network management virtualizer 100 filters or transforms (e.g., XSLT transforms) the EDIT-CONFIG RPC from the slice owner 110-S-1 before executing the RPC and applying the EDIT-CONFIG to the physical network datastore 1020. By contrast, the network management virtualizer 100 applies the EDIT-CONFIG RPC from the slice manager 110 directly to the physical network datastore 1020 without filtering or transformation.

Referring to FIG. 9A, the network management virtualizer 100 filters or transforms the EDIT-CONFIG RPC from the slice owner 110-S-1 by: 1) pruning the EDIT-CONFIG RPC from the slice owner 110-S-1 to validate that the EDIT-CONFIG RPC is not requesting modification of any network entities that are not classified as either create-able or allocate-able (XSLT classification pruning) in the classification metadata for the virtual network slice S-1; 2) pruning the EDIT-CONFIG RPC to validate that the EDIT-CONFIG RPC is not requesting modification of any network entities that are not allocated as read-write for the virtual network slice S-1 (XSLT allocation pruning); 3) validating the EDIT-CONFIG RPC to ensure that any other network slicing constraints are met (XSLT validation); and 4) tagging the EDIT-CONFIG RPC for any create-able entity types that are not allocated instances for read-write access (XSLT tagging). Example embodiments of XSLT classification pruning, XSLT allocation pruning, XSLT validation and XSLT tagging will be discussed in more detail below with regard to FIGS. 9B-9D.

FIG. 9B is a flow chart illustrating an example embodiment of the XSLT classification pruning shown in FIG. 9A. In discussing FIG. 9B, the EDIT-CONFIG RPC is referred to more generically as an edit request.

Referring to FIG. 9B, at step S900B the network management virtualizer 100 reads the next entity type from the list of create-able entity types in the classification metadata for the virtual network slice S-1.

At step S902B, the network management virtualizer 100 formulates an XSLT expression to prune the corresponding visible XML subtree(s) in the edit request based on the schema details for the current entity type in the classification metadata. The network management virtualizer 100 may formulate the XSLT expression in the same or substantially the same manner as discussed above with regard to step S702B in FIG. 7B.

At step S904B, the network management virtualizer 100 adds the XSLT expression to the XSLT transformation so that the create-able XML subtree(s) corresponding to the current entity type are kept and the rest are discarded when the XSLT transformation is applied to the edit request.

At step S906B, the network management virtualizer 100 determines whether the current entity type is the last entity type in the list of create-able entity types in the classification metadata.

If the current entity type is not the last entity type in the list of create-able entity types in the classification metadata, then the process returns to step S900B and the network management virtualizer 100 performs another iteration for the next entity type in the list of create-able entity types in the classification metadata.

Returning to step S906B, if the current entity type is the last entity type in the list of create-able entity types in the classification metadata, then the network management virtualizer 100 applies the XSLT transformation to the edit request at step S908B.

At step S910B, the network management virtualizer 100 determines whether the edit request has changed as a result of the application of the XSLT transformation. With regard to XML and XML documents, for example, the network management virtualizer 100 may determine whether the edit request has changed by comparing the original edit request with the transformed edit request after application of the XSLT transformation at run-time (e.g., in a computer program such as Java). According to at least one example embodiment, the network management virtualizer 100 may compare the original edit request with the transformed edit request by utilizing a library compareXML method. However, other methodologies may also be used. According to at least one other example embodiment, more complex XSLT in which validation over-and-above transforming the original XML message may also be used.

If the network management virtualizer 100 determines that the original edit request is the same as the transformed edit request (the transformation did not change the edit request), then at step S914B the network management virtualizer 100 forwards the original edit request for XLST allocation pruning.

Returning to step S910B, if the original edit request has changed as a result of the XSLT transformation at step S908B, then the network management virtualizer 100 rejects the edit request from the slice owner 110-S-1 at step S912B. According to at least one example embodiment, if the network management virtualizer 100 rejects the edit request, then the network management virtualizer 100 does not apply the requested changes and outputs an error-report.

FIG. 9C is a flow chart illustrating an example embodiment of the XSLT allocation pruning shown in FIG. 9A. In discussing FIG. 9C, the “EDIT-CONFIG” RPC is again referred to more generically as an edit request.

Referring to FIG. 9C, at step S900C the network management virtualizer 100 reads the next entity type from the list of allocate-able and create-able entity types in the classification metadata for the virtual network slice S-1.

At step S902C, the network management virtualizer 100 queries allocation metadata for corresponding instances of the current entity type from the physical network datastore 1020 based on the entity type identifier for the current entity type in the classification metadata.

If the network management virtualizer 100 finds instances of the current entity type as a result of the query of the allocation metadata at S904C, then at step S918C the network management virtualizer 100 uses the entity instance keys to formulate an XSLT expression to match the corresponding allocated XML instances of the current entity type in the edit request.

At step S906C, the network management virtualizer 100 adds the XSLT expression to the XSLT transformation so that unallocated instances, or allocated but not read-write accessible instances, are pruned from the edit request when the XSLT transformation is applied to the edit request.

At step S908C, the network management virtualizer 100 determines whether the current entity type is the last entity type in the list of allocate-able and create-able entity types.

If the network management virtualizer 100 determines that the current entity type is not the last entity type in the list of allocate-able and create-able entity types at step S908C, then the process returns to step S900C and the network management virtualizer 100 performs another iteration for the next entity type in the list of allocate-able and create-able entity types.

Returning to step S908C, if the current entity type is the last entity type in the list of allocate-able and create-able entity types, then at step S910C the network management virtualizer 100 applies the XSLT transformation to the edit request.

At step S912C, the network management virtualizer 100 determines whether the original edit request has changed as a result of the application of the XSLT transformation. The network management virtualizer 100 may determine whether the original edit request has changed in the same or substantially the same manner as discussed above with regard to step S910B in FIG. 9B.

If the edit request has not changed as a result of the application of the XSLT transformation, then at step S914C the network management virtualizer 100 forwards the original edit request for XSLT validation.

Returning to step S912C, if the original edit request has changed as a result of the application of the XSLT transformation, then at step S916C the network management virtualizer 100 rejects the original edit request.

Returning now to step S904C, if the network management virtualizer 100 does not find any corresponding instances of the current entity type as a result of the query at step S902C, then the process proceeds to step S908C and continues as discussed herein.

FIG. 9D is a flow chart illustrating an example embodiment of the XSLT validation shown in FIG. 9A. In discussing FIG. 9D, the NETCONF “EDIT-CONFIG” RPC is again referred to more generically as an edit request.

Referring to FIG. 9D, at step S900D the network management virtualizer 100 formulates a XSLT validation transformation based on constraints for the edit request. According to at least some example embodiments, constraints may include unsupported RPC operation types (e.g., a REPLACE or other operation that is not supported). Thus, in at least one example embodiment, the network management virtualizer 100 generates an XSLT validation transformation, which is a coding function, to remove unsupported operation types, types of datastores, etc., from the edit request.

At step S902D, the network management virtualizer 100 applies the XSLT validation transformation to the edit request to generate a transformed edit request. In the transformed edit request, if the edit request included an unsupported RPC operation type, then the unsupported RPC operation type may be pruned from the edit request to generate the transformed edit request.

At step S904D, the network management virtualizer 100 determines whether the original edit request is valid. In one example, the network management virtualizer 100 determines that the original edit request is valid if the transformed edit request is the same as the original edit request (the edit request does not change as a result of the application of the XSLT transformation at step S902D).

If the network management virtualizer 100 determines that the original edit request is valid (has not changed), then at step S908D the network management virtualizer 100 forwards the edit request for XSLT tagging.

Returning to step S904D, if the network management virtualizer 100 determines that the original edit request is not valid (has changed as a result of the applied XSLT transformation), then at step S906D the network management virtualizer 100 rejects the edit request.

In an alternative to the example embodiment shown in FIG. 9D, the XSLT transformation may return a true or false after checking for the presence of unsupported RPC operations. In this case, the network management virtualizer 100 may simply check the return value of the XSLT transformation, true or false, so as to validate the EDIT-CONFIG request. In yet another alternative, the unsupported RPC operations may be configurable, instead of being hard-coded in the logic of the source code.

FIG. 9E is a flow chart illustrating an example embodiment of the XSLT tagging shown in FIG. 9A. In discussing FIG. 9E, the NETCONF “EDIT-CONFIG” RPC is again referred to more generically as an edit request.

Referring to FIG. 9E, at step S900E the network management virtualizer 100 reads the next entity type from the list of allocate-able entity types in the classification metadata for the virtual network slice S-1.

At step S902E, the network management virtualizer 100 queries the allocation metadata for corresponding instances of the current entity type from the physical network datastore 1020 based on the entity type identifier for the current entity type in the classification metadata.

If the network management virtualizer 100 finds instances of the current entity type as a result of the query of the allocation metadata for instances of the current entity type at step S904E, then at step S906E the network management virtualizer 100 uses the corresponding entity instance keys to formulate an XSLT expression to prevent tagging of the corresponding allocated entity instances when the XSLT transformation is applied to the edit request.

At step S908E, the network management virtualizer 100 adds the XSLT expression to an XSLT transformation so that allocated entity instances are not tagged when the XSLT transformation is applied to the edit request.

At step S910E, the network management virtualizer 100 determines whether the current entity type is the last entity type in the list of allocate-able entity types.

If the current entity type is not the last entity type in the list of allocate-able entity types, then the process returns to step S900E and another iteration of the process is performed for the next entity type in the list of allocate-able entity types.

Returning to step S910E, if the current entity type is the last entity type in the list of allocate-able entity types, then at step S912E the network management virtualizer 100 reads the next entity type from the list of create-able entity types in the classification metadata for the virtual network slice S-1.

At step S914E, the network management virtualizer 100 refines the XSLT expression for the next entity type in the list of create-able of entity types based on schema details for the current entity type to tag the next entity type if the current entity type is not listed as an instance in the allocation metadata.

At step S916E, the network management virtualizer 100 adds the refined XSLT expression to the XSLT transformation. In so doing, if the current entity type is create-able, but not listed as an allocated instance, then the network management virtualizer 100 tags the current entity type when the XSLT transformation is applied to the edit request.

The network management virtualizer 100 determines whether the current entity type is the last network entity type in the list of create-able entity types in the classification metadata at step S918E.

If the current entity type is not the last entity type in the list of create-able network entity types, then the process returns to step S912E and continues as discussed herein for the next entity type in the list of create-able network entity types.

Returning to step S918E, if the current entity type is the last entity type in the list of create-able entity types, then at step S920E the network management virtualizer 100 applies the XSLT transformation to the edit request.

The transformed edit request is then forwarded to the physical network datastore 1020 at step S922E to configure (or edit the configuration of) the virtual network slice S-1. In at least one example embodiment, the transformed edit request may result in creation of a network entity (with the designated configuration) in the virtual network slice S-1. In another example, the transformed edit request may overwrite an existing configuration for an existing network entity in the virtual network slice S-1 (edit the configuration of the network entity).

An optional transformation of EDIT-CONFIG requests in at least one example embodiment may support allowing slice owners to create entity instances based on allocation metadata. In this case, the slice manager 110 may grant write-access to a slice owner for an entity instance with a specific key value, but the slice manager 110 does not create the entity instance with said key value. Instead, the slice owner may create the entity instance based on the allocation metadata, using the specified key value, and based on the fact that the corresponding entity type is listed as access-configurable in the classification metadata. This is in contrast to only allowing the slice owner to create entity instances based on the classification metadata list of create-able entity types.

An optional transformation of GET-CONFIG responses in accordance with at least one example embodiment may keep visible entity instances created by the slice manager 110 by default in any virtual network slice, where the corresponding entity types are not listed in the classification metadata at all, and there is no corresponding reference to these instances in the allocation metadata. In contrast, another different approach may not support this default visibility. That is, for example, unless an entity instance in a GET-CONFIG response has a corresponding entity type entry in the classification metadata (either access-configurable or create-able), then it is not visible in the GET-CONFIG response of a virtual network slice.

The XSLT technology used to transform the EDIT-CONFIG requests and responses is flexible, and thus, the manner in which change requests and responses are filtered or transformed against the classification and allocation metadata may be varied.

According one or more example embodiments, when a slice owner is configuring or editing configuration of network nodes (e.g., entities, entity instances, etc.) in a virtual network slice, the network management virtualizer 100 may validate changes to the virtual network slice based on additional user-defined rules expressed in a data-driven manner. For example, XQuery metadata rules may be expressed in the classification and allocation metadata so as to limit the range of virtual local area network (VLAN) identifiers (IDs) used in a virtual network slice. The XQuery rules may be arbitrarily defined based on the user requirements for the virtual network slice. The validation engine may be data-driven by the XQuery rules defined in the model-based classification metadata, combined with corresponding slice-specific values or limits in the allocation metadata. This enables the simpler application of rules via changes in the configurable metadata, rather than changes in code. A validation engine performs the validation during a physical network datastore validation phase (e.g., after changes are applied to generate the candidate physical network datastore, but before the changes are exposed to slice owners and the slice manager). This phase provides the opportunity to either accept or reject the changes and rollback to the physical network datastore prior to the changes if necessary. Some of the validation may be hard-coded (e.g., in Java using XSLT libraries) or driven by the virtual network slice classification and allocation metadata. The additional XQuery validation XML configuration may also be driven by the virtual network slice classification and allocation metadata. In at least one example, user-defined refers to defined by the slice manager 110 user via virtual network slice classification and allocation metadata configuration.

Edit requests such as EDIT-CONFIG RPCs from slice owners may also be validated to enforce maximum limits of entity instances per virtual network slice.

The network management virtualizer 100 may validate changes by validating a “candidate datastore.” An example of a candidate datastore is specified in RFC 6421 by the IETF. A candidate datastore or candidate configuration datastore holds configuration data that may be manipulated without impacting a network entity's current configuration.

FIG. 10 is a flow diagram illustrating a method for candidate datastore validation, according to one or more example embodiments. FIGS. 11, 12A and 12B are flow charts illustrating methods for candidate datastore validation, according to one or more example embodiments. For example purposes, FIGS. 11-12B are described more generically with regard to an edit request, rather than a RPC such as the “EDIT-CONFIG” RPC. Moreover, the example embodiments shown in FIGS. 11-12B will be discussed with regard to an edit request from the slice owner 110-S-1. However, it should be understood that the same or substantially the same validation procedure may be performed in response to edit (or other) requests from the slice manager 110.

In this example, once all modifications are applied to the candidate datastore based on one or more edit requests (e.g., EDIT-CONFIG RPCs) from the slice owner 110-S-1, a validation of the result is performed before the changes are committed to the actual physical network datastore 1020. One example constraint that may be enforced using this methodology is maximum bandwidth usage per PON port per virtual network slice.

Referring to FIGS. 10 and 11, at step S1104 the network management virtualizer 100 applies the changes for the virtual network slice S-1 specified in the edit request to the candidate datastore.

At step S1106, the network management virtualizer 100 determines whether the modified candidate datastore is valid by performing validation of referential integrity among others. For example, the network management virtualizer 100 validates whether any entity instance reference in the modified candidate datastore points to an existing corresponding entity instance entry in the candidate datastore, such that there cannot exist a reference without its corresponding entity instance entry in the candidate datastore.

If the modified candidate datastore is not valid, then at step S1122 the network management virtualizer 100 sends a reply (e.g., a query response) indicating that the validation procedure has failed. In this case, the requested changes are not committed to the actual physical network datastore 1020 and the process terminates.

Returning to step S1106, if the network management virtualizer 100 determines that the modified candidate datastore is valid, then at step S1108 the network management virtualizer 100 processes the query response as discussed above with regard to FIGS. 7A-7D. That is, for example, the network management virtualizer 100 performs XSLT classification pruning, XSLT allocation tagging and XSLT tag processing on the query response.

At step S1116, the network management virtualizer 100 determines whether the resultant virtual network slice view of the modified candidate datastore is valid based on the processed query response. In one example, the network management virtualizer 100 validates the partitioning limits of the virtual network slice S-1 (e.g., limits on the number of network entities created in the scope of a virtual network slice by a slice owner), which may be provisioned by the slice manager 110. These limits may be an optional part of the allocation metadata. Other forms of limits may be enforced via user-defined rules, using generic XQuery expressions in classification metadata combined with corresponding slice-specific limits in allocation metadata. These include, but are not limited to, the virtual network slice bandwidth usage on a port. Methods for determining whether the resultant network slice view of the modified candidate datastore is valid will be discussed in more detail below with regard to FIGS. 12A and 12B.

If the network management virtualizer 100 determines that the resultant network slice view is valid, then at step S1118 the network management virtualizer 100 commits the requested changes to the physical network datastore 1020. The network management virtualizer 100 then outputs the query response indicating that the validation of the virtual network slice view was successful at step S1120.

Returning to step S1116, if the network management virtualizer 100 determines that the resultant network slice view is not valid, then the network management virtualizer 100 proceeds to step S1122 and continues as discussed above.

FIG. 12A is a flowchart illustrating a method for determining whether the resultant network slice view of the candidate physical network datastore is valid, according to one or more example embodiments. For example purposes, the method shown in FIG. 12A will be discussed with regard to partition limit values for a network entity in the virtual network slice S-1 in FIG. 1. However, the method shown in FIG. 12A may be applicable to other operations.

Partitioning is a relatively simple type of validation and refers to limiting the number of entities of a certain type that can be created within a slice. For example, one may specify the maximum number of ONTs that may be created in a virtual network slice.

Referring to FIG. 12A, at step S2000 the network management virtualizer 100 obtains the partition limit values from the allocation metadata for the entity type.

At step S2002, the network management virtualizer 100 applies partition limit values to the generic validation expressions stored in the classification metadata for the virtual network slice S-1.

Partition limit expressions are relatively simple and deal with limiting the creation of instances of a given type. In contrast, user-defined validation expressions are generic XQuery expressions that may perform more complex checks, such as summing up an attribute value across a filtered list of resources within the virtual network slice and comparing the sum with a configurable limit. For example, one can specify an upper limit for the configured committed bit-rate (attribute value) of all user-to-network interfaces (filtered list of resources) created in a virtual network slice. The generic XQuery expressions are specified in the classification metadata based on the model of the device. The generic XQuery expression is combined with corresponding values or limits specified in the allocation metadata corresponding to a slice instance in a device instance. This enables the same model-based generic XQuery expression to be applied differently on a slice-instance basis.

At step S2004, the network management virtualizer 100 evaluates the partition limit expressions against the virtual network slice view of the candidate datastore to determine whether the candidate datastore is still within the partition limits obtained from the allocation metadata. For example, the network management virtualizer 100 counts the created entity instances within the virtual network slice and compares the count with the configured partition-limit.

If the network management virtualizer 100 determines that the candidate datastore is still within the partition limits obtained from the allocation metadata at step S2006 (e.g., number of entities is less than or equal the partition limit) then the network management virtualizer 100 determines that the candidate datastore is valid (validation successful) at step S2008.

Returning to step S2006, if the network management virtualizer 100 determines that the candidate datastore is no longer within the partition limits obtained from the allocation metadata (e.g., number of entities is greater than the partition limit), then the network management virtualizer 100 determines that the candidate physical network datastore is invalid (validation failed) at step S2010.

FIG. 12B is a flowchart illustrating a method for determining whether the resultant virtual network slice view of the candidate datastore is valid based on user-defined validation XQuery expressions according to one or more example embodiments. In this example, the user may be the slice manager 110. For example purposes, the method shown in FIG. 12B will be discussed with a network entity in the virtual network slice S-1 in FIG. 1.

Referring to FIG. 12B, at 52100 the network management virtualizer 100 combines user-defined validation values (e.g., limits, etc.) from the allocation metadata with a corresponding generic XQuery expression in the classification metadata.

At step S2102, the network management virtualizer 100 applies user-defined values to the generic validation expressions stored in the classification metadata for the virtual network slice S-1. In this example, the user (e.g., slice manager 110) specifies a VLAN identifier range (e.g., minimum identifier value and maximum identifier value) as arguments of the corresponding XQuery validation expression.

At step S2104, the network management virtualizer 100 evaluates the user-defined expressions against the virtual network slice view of the candidate physical network datastore to determine whether the virtual network slice view of the candidate datastore is valid. The evaluation at step S2104 may be the same or substantially the same as step S2004 in FIG. 12A.

If the network management virtualizer 100 determines that the virtual network slice view of the candidate datastore is valid at step S2106, then the network management virtualizer 100 determines that the candidate datastore is valid (validation successful) at step S2108.

Returning to step S2106, if the network management virtualizer 100 determines that the virtual network slice view of the candidate datastore is not valid, then the network management virtualizer 100 determines that the virtual network slice view of the candidate datastore is not valid (validation failed) at step S2110.

According to one or more example embodiments, the network management virtualizer 100 may send autonomous notifications (e.g., NETCONF notifications) to slice owners. A state change in the network management virtualizer 100 may cause the network management virtualizer 100 to output an autonomous notification. In at least one example embodiment, a state change may include a network device becoming unreachable, a change in the configuration of a network device, etc. When these states are relevant for a virtual network slice, the network management virtualizer 100 may send a notification to the corresponding slice owner.

The network management virtualizer 100 may XSLT-transform the autonomous notifications from the physical network datastore to the projected virtual network slice view. By contrast, the network management virtualizer 100 may send the same autonomous notifications directly to the slice manager 110 without filtering or XSLT-transformation. In at least one example embodiment, autonomous notifications may include operational information from the network, rather than network configuration information from the physical network datastore 1020.

FIG. 13 is a flow diagram illustrating a method for autonomous notification according to one or more example embodiments. FIG. 14 is a flow diagram illustrating the XSLT transformation performed on an autonomous notification from the network management virtualizer 100 to the slice owner 110-S-1 in more detail. For example purposes, FIGS. 13 and 14 will be discussed with regard to NETCONF notifications. However, example embodiments may be applicable to other network management protocols such as SNMP.

According to one or more example embodiments, a slice manager may receive performance monitoring notifications, alarm notifications, status update notifications, etc., for any/all network entities, whereas a slice owner may receive said notifications for only network entities visible in the virtual network slice view.

Referring to FIGS. 13 and 14, the XSLT transformations applied to the autonomous NETCONF notifications include XSLT classification pruning, XSLT allocation tagging and XSLT tag processing. These XSLT transformations are substantially the same as those discussed above with regard to FIGS. 7A-7D, except that the XSLT transformations are applied to operational information for the physical network, rather than the network configuration information. Because the XSLT transformations are the same as those discussed above with regard to FIGS. 7A-7D, a detailed discussion is omitted.

FIG. 15 is a diagram illustrating classification of entity types for virtual network slice filtering according to one or more example embodiments.

Referring to FIG. 15, “Entities visible in slices” define subtrees and leaves of entities that are visible in slices based on entity types in the management model. This may be specified for the management model as well as individual device type models.

“Entities allocate-able in slices” define the network entities (e.g., via a list) that may be allocated to a virtual network slice by the slice manager using allocation metadata. A given entity instance in the allocation metadata is linked via the “slice entity type identifier” to the corresponding entity classification metadata. As shown in FIG. 15, the classification metadata for an entity includes a slice entity type identifier, schema details and a key attribute name.

“Entities create-able in slices” define the network entities (e.g., via a list) that may be created by a slice owner or created and allocated by a slice manager. If created by a slice owner, then the network entities may be key tagged in the physical network datastore to associate the network entity with one or more virtual network slices. These network entities may be specified using the local name and name space of the subtree root node representing the network resource. According to one or more example embodiments, a subtree leaf and its value may be used to discriminate among sub-types of the same entity type. This may be useful in the case where entities of type “interface” and sub-type “A” may be created by the slice owner, but entities of type “interface” and sub-type “B” may not be created by the slice owner. If no discriminator leaf and value is specified, then all entities of type “interface” may be created by the slice owner.

A subset of “Entities create-able in slices” are subtree leaves that refer to other entities using the YANG leaf-ref construct (also referred to as entity references). Entity references utilize a “referential integrity” validation in order to ensure that the network entity pointed to exists and is accessible within the same virtual network slice.

One or more example embodiments enable delegating referential integrity validation to the physical network datastore NETCONF request processing (e.g., the default NETCONF stack). If the slice owner specifies an entity reference in a request for an entity instance that is not explicitly allocated in the virtual network slice, then it is assumed that the entity instance must have been created by the slice owner and the instance key in the entity reference is automatically tagged in the XSLT transformation. If the entity instance being referred to was not created by the slice owner, then the default NETCONF stack will validate and fail the request as it will not find an instance with the specified tagged key. This may provide an improvement over performing redundant referential integrity validation in a projected slice view in addition to the physical network datastore.

FIG. 16 is a diagram depicting an example embodiment of a structure of entity allocation metadata. This approach of explicitly assigning instances of network entities to virtual network slices is similar to Flowvisor in Software-Defined Networks (SDN) using OpenFlow. In at least this implementation, “Entity allocation metadata” is used to complement “Entity type classification metadata” and key tagging.

FIG. 17 is a flowchart illustrating a method of configuring entity classification and entity allocation metadata according to one or more example embodiments.

Referring to FIG. 17, at step S1700 the network engineer configures the entity classification metadata for an entity instance. In this example, the network engineer specifies that the entity type for the entity instance is visible and allocate-able. As shown, the entity classification metadata for entity type X includes a slice entity type identifier X, schema details and a key attribute name.

At S1702, the slice manager then creates instance Y of the entity type X and configures the allocation metadata for entity instance Y based on the entity classification metadata configured by the network engineer. In at least one example embodiment, the slice entity type identifier X is referenced from the entity allocation metadata to the entity classification metadata.

As a result of the example embodiment shown in FIG. 17, instance Y of entity type X is read-write accessible to the slice owner(s) of the given virtual network slice. That is, for example, attributes of instance Y may be modified by the slice owner(s) of the given virtual network slice.

As discussed in detail above, the classification metadata and the allocation metadata for a given entity instance drive the XSLT-transformations used to project the slice view of the physical network datastore to the slice owner.

FIG. 18 is a flowchart illustrating a method for driving key tagging of entity instances created by a slice owner using classification metadata, according to one or more example embodiments. For example purposes, the flowchart in FIG. 18 will be described with regard to creation of entity instance W and entity type Z in a virtual network slice.

Referring to FIG. 18, at step S1800 a network engineer configures the classification metadata to specify that device entity types with device entity type identifier Z (device entity type Z) are both visible and create-able. The network engineer may configure the device classification metadata at step S1800 in the same or substantially the same mariner as at step S1700.

At S1802, the slice owner creates the entity instance W of entity type Z in the virtual network slice based on the classification metadata configured at step S1800. Accordingly, the entity instance W is visible and create-able in the virtual network slice.

As a result of the example embodiment shown in FIG. 18, the instance W of the entity type Z is stored in the physical network datastore and tagged with a tag corresponding to the virtual network slice, and instance W of entity type Z is read-write accessible by slice owner(s) of the virtual network slice; that is, for example, attributes of instance W may be modified or deleted by slice owner(s) of the virtual network slice, and other instances of entity type Z may be created by slice owner(s) of the virtual network slice.

Recursive or hierarchical slicing may be supported as defined in Network Slicing Architecture draft-geng-netslices-architecture-01 dated Jun. 2, 2017 by the Internet Engineering Task Force (IETF) Network Working Group (NWG). In this case, a slice owner in the first level of slicing acts as a slice manager for the second level of slicing. Tags are incrementally applied to key values from one level to the next.

The centralized physical network datastore maintains a master copy of all network management virtualizer and device-specific data for all devices in the scope of the network manager. There is no data duplication in the sense that a single master copy is maintained for the scope of the network management virtualizer and all devices in that scope. However, this does not prevent data from being disseminated from the network management virtualizer to individual devices as needed for the devices to operate. A device may or may not persist its slave copy of the data as needed for its operation. The slave data is not considered duplicated for the purposes of example embodiments given that the single centralized master copy is the only reference data used and enforced across all devices.

The centralized physical network datastore may optionally be distributed, while maintaining a single master copy of the data in either centralized or distributed manner. An example of distributed datastore involves having each network device maintain a master copy of its own data, instead of having the network management virtualizer maintain a master copy of all device-specific data for all devices. The same network slicing solution applies except that the validation of changes applied to the datastore on the device has to be performed on the device. In this case, the device should be slice aware for slicing-specific validation to be performed on the device. Alternately, slicing-specific datastore validation may either be omitted or performed against the edit requests only in the network management virtualizer using a different approach (e.g., a request-based validation approach instead of datastore-based validation approach).

A slice owner may not have access to all NETCONF RPC types. Typically, a slice owner may only be authorized to access a subset of all RPC types (e.g., GET, GET-CONFIG, EDIT-CONFIG, but not COPY-CONFIG, etc.). User management authentication and authorization is also used to identify slice owners and manage slice owner access to a specific slice, via the various network management virtualizer user-accessible interfaces. Similarly, authentication and authorization may be used to manage the slice manager access.

FIG. 20 is an embedded flow diagram illustrating a method for autonomous notification according to one or more example embodiments. FIG. 21 is an embedded flow diagram illustrating autonomous provisioning of operational data according to one or more example embodiments. As shown, the flow diagrams in FIGS. 20 and 21 are embedded in a portion of the physical network architecture shown in FIG. 1. The portion of the network architecture shown in FIGS. 20 and 21 includes: network node 104-1, which is associated with virtual network slice S-1 in FIG. 1; the slice owner 110-S-1, virtual network slice S-1; the slice manager 110; and network management virtualizer 100. Although only node 104-1 is shown in FIGS. 20 and 21, it should be understood that the physical network may include any number of nodes (e.g., nodes 104-1 through 104-m from FIG. 1).

For example purposes, FIGS. 20 and 21 will be discussed with regard to NETCONF notifications. However, example embodiments may be applicable to other network management protocols such as SNMP.

According to one or more example embodiments, a slice manager may receive performance monitoring notifications, alarm notifications, status update notifications, operational data, etc., for any and/or all network entities configured for the network, whereas a slice owner may receive said notifications and/or operational data for only network entities (also referred to as entity instances or network entity instances) visible in the virtual network slice view. As discussed herein, notifications, alarm notifications, status update notifications, operational data, etc., may be included in a network information message.

According to one or more example embodiments, the network management virtualizer 100 may filter and transform autonomous notifications based on classification metadata by matching the pertaining entity instance to a specific entity type entry in the classification metadata. In cases in which not enough information is included within the notification (or operational data), the network management virtualizer 100 may use a mapping to link (e.g., directly link) or match an entity instance to its corresponding entry in the classification metadata. Once the entry (entity type) is identified, the network management virtualizer 100 uses the entry to drive the process of determining whether the entity instance, notification and/or operational data should be visible to a slice owner within a virtual network slice.

According to one or more example embodiments, autonomous notifications may be received at the network management virtualizer 100 in batches. In one example, a single network information message (also referred to in this instance as a notification message) may include a set of notification entries as opposed to a single notification entry, wherein the set of notification entries may include multiple notifications from an entity instance or multiple notifications from multiple entity instances. In this case, methods according to one or more example embodiments (e.g., as illustrated in FIGS. 22 and 23) may be performed for each notification entry, one at a time, or concurrently (where the original set order may be maintained or not depending on implementation).

FIG. 22 is a flow chart illustrating a method for autonomous notification according to one or more example embodiments. The method shown in FIG. 22 may be performed at the network management virtualizer 100 and will be discussed with regard to the embedded flow diagram shown in FIG. 20. The method shown in FIG. 22 may be implemented using XSLT, XQuery, XPath, Document Object Model (DOM) or related technologies if autonomous notifications are XML-encoded. Otherwise, any technology pertinent to the encoding may be used.

Referring to FIG. 22, at step S2200 the network management virtualizer 100 receives a network information message including an autonomous notification from node 104-1 in the network.

At step S2202, the network management virtualizer 100 scans the notification content to identify the entity instance, configured within node 104-1, having originated the autonomous notification received at step S2200. In at least one example embodiment, an entity instance may be identified within an XPath expression in the network information message. This expression may be linked to a corresponding entity type entry in the classification metadata. At step S2204, the network management virtualizer 100 retrieves, from the physical network datastore 1020, the classification metadata for the virtual network slice S-1 associated with the entity instance.

At step S2206, the network management virtualizer 100 attempts to match the entity instance identified in step S2202 to a corresponding entity type in the classification metadata retrieved at step S2204. In at least one example embodiment, the network management virtualizer 100 may attempt to match the entity instance to a corresponding entity type by comparing the schema information from the autonomous notification with the schema details for corresponding entity types. In one example, an XPath expression in the autonomous notification may be matched to classification metadata entity type schema details (e.g., schemapath) via a path to path comparison.

At step S2208, the network management virtualizer 100 determines whether there is an entity type matching the entity instance. If the network management virtualizer 100 determines, based on the comparison, that the schema information from the autonomous notification matches the schema details for a corresponding entity type in the classification metadata, then the network management virtualizer 100 determines that the entity instance matches that corresponding entity type.

According to one or more example embodiments, the network management virtualizer 100 may not find an exact match in cases where the schema details for an entity type from the classification metadata are more granular than then schema information available in the autonomous notification received. This may result in ambiguity, where entries of multiple entity types in the classification metadata are possible matches to the identified entity instance. The network management virtualizer 100 may also not find a match in cases where the available schema details from the autonomous notification simply do not match schema details for any entity types in the classification metadata.

If the network management virtualizer 100 does not find an exact match for the entity instance identified at step S2208, then at step S2210 the network management virtualizer 100 attempts to retrieve the entity instance identified in step S2202 from a cached mapping or cached map between configured network resources and classification metadata by querying the cached mapping or cached map. The network management virtualizer 100 maintains the cached mapping in the background to link entity instances stored at the physical network datastore 1020 to entity types in the classification metadata for the virtual network slice S-1. The network management virtualizer 100 maintains the cached mapping by identifying and storing links as new entity instances are added to the physical network datastore 1020. The entity type may be determined unambiguously at the time the entity instance is added based on the level of schema details available at this time. In comparison, this same level of detail may not be always available in autonomous notifications originating from the same entity instance at a later time. The network management virtualizer 100 may remove links from the cached mapping in response to removal of entity instances from the physical network datastore 1020. If the network management virtualizer 100 determines that there is a match for the entity instance in the cached mapping at step S2212 (e.g., if an entry key in the stored mapping matches the XPath expression for the notification), then at step S2214 the network management virtualizer 100 checks the identified entity type to determine whether the identified entity type is classified as create-able (e.g., belongs in the create-able category).

If the identified entity type is create-able, then at step S2216 the network management virtualizer 100 checks the entity instance key value included in the received autonomous notification to determine whether the entity instance key value is prefixed. The prefix is specified in the allocation metadata for the virtual network slice S-1 stored at the physical network datastore 1020. The prefix identifies the entity instance as belonging to, and read-write-able from within, virtual network slice S-1, without ambiguity.

If the entity instance key value is prefixed, then at step S2218 the network management virtualizer 100 removes the prefix from the entity instance key value from the autonomous notification to generate a transformed autonomous notification for delivery to the slice owner 110-S-1.

At step S2220, the network management virtualizer 100 forwards the transformed autonomous notification to be dispatched to the slice owner 110-S-1 corresponding to the virtual network slice S-1 stored at the physical network datastore 1020.

Returning to step S2216, if the entity instance key value is not prefixed, then at step S2224 the network management virtualizer 100 checks the allocation metadata for the virtual network slice S-1 stored at the physical network datastore 1020 to determine whether the entity instance is configured as visible in the allocation metadata; for example, whether the entity instance is allocated to the virtual network slice S-1.

If the entity instance is configured as visible in the allocation metadata, then the process proceeds to step S2220 and continues as discussed herein.

Returning to step S2224, if the entity instance is not configured as visible in the allocation metadata, then at step S2228 the network management virtualizer 100 discards the autonomous notification so that the autonomous notification is not dispatched to the slice owner 110-S-1 of the virtual network slice S-1.

Returning to step S2214, if the identified entity type is not create-able, then at step S2222 the network management virtualizer 100 checks the identified network entity type to determine whether the identified network entity type belongs in classified as allocate-able (in the allocate-able category).

If the identified network entity is classified as allocate-able, then the process proceeds to step S2224 and continues as discussed herein.

Returning to step S2222, if the identified entity type is not classified as allocate-able, then at step S2226 the network management virtualizer 100 checks the identified entity type to determine whether the identified entity type belongs is classified as within the notification scope for the virtual network slice S-1 (in the notification scope category). As discussed in more detail below with regard to FIG. 26, the classification metadata may include “Entities in the notification scope of slices” entries indicating whether an entity instance is in the notification scope of a virtual network slice. If an entity instance is within the notification scope, then autonomous notifications are visible by a slice owner of the virtual network slice.

If the identified entity type is classified as within the notification scope, then the process proceeds to step S2220 and continues as discussed above.

Returning to step S2226, if the identified entity type is not classified as within the notification scope for the virtual network slice S-1, then the process proceeds to step S2228 and continues as discussed above.

Returning to step S2212, if the network management virtualizer 100 determines that there is not a match for the entity instance in the cached mapping, then the process proceeds to step S2228 and continues as discussed above.

Returning now to step S2208, if the network management virtualizer 100 determines that there is an entity type in the classification metadata matching the entity instance identified at step S2202, then the process proceeds to step S2214 and continues as discussed herein.

Although shown in FIG. 22, steps S2210 and S2212 may be omitted. In this case, if no match is found at step S2208, then the process proceeds to step S2228 and continues as discussed above.

FIG. 23 is a flow chart illustrating a method for autonomous notification according to one or more example embodiments. The method shown in FIG. 23 may be performed at the network management virtualizer 100. The method shown in FIG. 23 may be performed at the network management virtualizer 100 and will be discussed with regard to the embedded flow diagram shown in FIG. 20. As with the example embodiment shown in FIG. 22, the steps in the method shown in FIG. 23 may be implemented using XSLT, XQuery, XPath, Document Object Model (DOM) or related technologies if autonomous notifications are XML-encoded. Otherwise, any technology pertinent to the encoding may be used.

Referring to FIG. 23, at step S2300 the network management virtualizer 100 receives an autonomous notification from node 104-1.

At step S2302, the network management virtualizer 100 attempts to retrieve a slice view (S-1 datastore virtual view) for the virtual network slice S-1 from a cache in the physical network datastore 1020. The network management virtualizer 100 may obtain the slice view using, for example, GET-CONFIG as illustrated in, for example, FIG. 5. Slice views may be optionally be cached for efficiency.

If a slice view for the virtual network slice S-1 is present in the cache, then at step S2304 the network management virtualizer 100 retrieves the slice view for the virtual network slice S-1 from the cache.

At step S2306, the network management virtualizer 100 obtains a matching (e.g., XPath) query expression based on the entity instance information available in the received autonomous notification. The expression allows for the optional presence of a prefix in the key value of the entity instance such that a matching entity instance may be found in the slice view with or without a prefix.

At step S2310, the network management virtualizer 100 executes the query against the slice view.

At step S2314, the network management virtualizer 100 checks the result of the execution of the XPath query at step S2310 to determine if there is a matching entity instance in the slice view. This indicates whether the entity instance is visible in the slice view.

If there is not a matching entity in the slice view, then at step S2328 the network management virtualizer 100 discards the autonomous notification so that the autonomous notification is not dispatched to the slice owner 110-S-1 of the virtual network slice S-1 stored at the physical network datastore 1020.

Returning to step S2314, if the network management virtualizer 100 determines that there is a matching entity instance in the slice view, then at step S2316 the network management virtualizer 100 checks the key value for the entity instance included in the received autonomous notification to determine whether the entity instance is prefixed. The network management virtualizer 100 determines whether the key value for the entity instance is prefixed in the same or substantially the same manner as discussed above with regard to step S2216 in FIG. 22.

If the key value for the entity instance is prefixed, then at step S2318 the network management virtualizer 100 removes the prefix from the key value in the autonomous notification to generate the transformed autonomous notification. The network management virtualizer 100 removes the prefix in the same or substantially the same manner as discussed above with regard to step S2218 in FIG. 22.

At step S2320, the network management virtualizer 100 then forwards the transformed autonomous notification to be dispatched to the slice owner 110-S-1 of to the virtual network slice S-1 stored at the physical network datastore 1020.

Returning to step S2316, if the entity instance is not prefixed, then the process proceeds to step S2320 and continues as discussed above.

Returning to step S2302, if a slice view for the virtual network slice S-1 is not present in the cache, then at step S2308 the network management virtualizer 100 obtains the slice view for the virtual network slice S-1 (e.g., according to the process illustrated in FIG. 5 using GET-CONFIG) from the physical network datastore 1020. Also at step S2308, the network management virtualizer 100 stores the obtained slice view in the cache. The process then proceeds to step S2306 and continues as discussed herein.

Although discussed separately, the example embodiments shown in FIGS. 22 and 23 may be implemented in combination with one another and/or used interchangeably.

One or more example embodiments also provide methods for autonomous provisioning of operational data to slice owners. According to at least one example embodiment, the network management virtualizer 100 may utilize classification metadata to filter and transform received operational data (e.g., received via a network information message) by matching the pertaining entity instance to an entry in the classification metadata. XSLT or Document Object Model (DOM) technologies may be used to filter or transform XML-encoded operational data.

In cases where not enough information is included within the received operational data, a mapping may be used to link (e.g., directly link) an entity instance to a corresponding entry in the classification metadata. Once the entry is identified, the entry is used to drive the process of determining whether the entity instance is visible within the slice or not.

If the entry in the classification metadata corresponds to a create-able entity type, then the network management virtualizer 100 checks whether the key value for the entity instance is prefixed. If the key value is not prefixed, then the network management virtualizer 100 determines whether the entity instance is visible in the virtual network slice based on allocation metadata. If the entity instance is not visible in the virtual network slice, then the received operational data is discarded. Otherwise, the received operational data is forwarded on to the slice owner.

If the entry in the classification metadata corresponds to an allocate-able entity type, then the network management virtualizer 100 checks whether the entity instance is visible in the virtual network slice based on allocation metadata. If the entity instance is not visible, then the received operational data is discarded. Otherwise, the network management virtualizer 100 forwards the received operational data to the slice owner.

If the classification metadata entry corresponds to an entity type classified as within the notification scope for the virtual network slice, then the received operational data is forwarded without further checks. Otherwise, the received operational data is discarded.

According to one or more example embodiments, operational data may be received at the network management virtualizer 100 in batches. In one example, a single network information message may include a set of operational data entries as opposed to a single operational data entry, wherein the set of operational data entries may include operational data for multiple entity instances. In this case, methods according to one or more example embodiments (e.g., as illustrated in FIGS. 24-25) may be performed for each operational data entry, one at a time, or concurrently (where the original set order may be maintained or not depending on implementation).

FIG. 24 is a flow chart illustrating a method for autonomous provisioning of operational data according to one or more example embodiments. The method shown in FIG. 24 may be performed at the network management virtualizer 100. As with the example embodiment shown in FIGS. 22 and 23, the steps in the method shown in FIG. 24 may be implemented using XSLT, XQuery, XPath, Document Object Model (DOM) or related technologies if autonomous notifications are XML-encoded. Otherwise, any technology pertinent to the encoding may be used. Referring to FIG. 24, at step S2400 the network management virtualizer 100 receives operational data from node 104-1. Operational data may be communicated via NETCONF GET query/response, NETCONF autonomous notification, IPFIX notifications, or any other suitable protocol.

At step S2402, the network management virtualizer 100 scans the content of the operational data (e.g., as set forth in the NETCONF GET, NETCONF autonomous notification, IPFIX notification, etc.) to identify the entity instance, configured within node 104-1, having originated the autonomous notification received at step S2400.

At step S2404, the network management virtualizer 100 retrieves the classification metadata for the virtual network slice S-1 stored at the physical network datastore 1020.

At step S2406, the network management virtualizer 100 attempts to match the entity instance identified in step S2402 to a corresponding entity type in the classification metadata retrieved at step S2404. In at least one example embodiment, the network management virtualizer 100 may attempt to match the entity instance to a corresponding entity type by comparing the schema information from the received operational data with the schema details for corresponding entity types.

At step S2408, the network management virtualizer 100 determines whether there is an entity type in the classification metadata matching the entity instance in the same or substantially the same manner as discussed above with regard to step S2208 in FIG. 22.

If the network management virtualizer 100 does not find an exact match for the entity instance identified at step S2408, then at step S2410 the network management virtualizer 100 attempts to retrieve the entity instance from a cached mapping (also referred to as a cached map) between configured entity instances and classification metadata. As discussed above with regard to FIG. 22, the network management virtualizer 100 maintains the cached mapping in the background to link entity instances stored at the physical network datastore 1020 to entity types in the classification metadata for the virtual network slice S-1.

If the network management virtualizer 100 determines that there is a match for the entity instance in the cached mapping at step S2412, then at step S2414 the network management virtualizer 100 checks the identified entity type to determine whether the identified entity type is classified as create-able (e.g., belongs in the create-able category).

If the identified entity type is classified as create-able, then at step S2416 the network management virtualizer 100 checks the entity instance key value included in the received operational data to determine whether the entity instance key value is prefixed. As discussed above with regard to the example embodiment shown in FIG. 22, the prefix is specified in the allocation metadata for the virtual network slice S-1 stored at the physical network datastore 1020. The prefix identifies the entity instance as belonging to, and read-write-able from within, virtual network slice S-1, without ambiguity.

If the entity instance key value is prefixed, then at step S2418 the network management virtualizer 100 removes the prefix from the entity instance key value from the received operational data to generate transformed operational data for delivery to the slice owner 110-S-1.

At step S2420, the network management virtualizer 100 forwards the transformed operational data to be dispatched to the slice owner 110-S-1 corresponding to the virtual network slice S-1 stored at the physical network datastore 1020.

Returning to step S2416, if the entity instance key value is not prefixed, then at step S2424 the network management virtualizer 100 checks the allocation metadata for the virtual network slice S-1 stored at the physical network datastore 1020 to determine whether the entity instance is configured as visible in the allocation metadata; that is, for example, the entity instance is allocated to the virtual network slice S-1.

If the entity instance is configured as visible in the allocation metadata, then the process proceeds to step S2420 and continues as discussed herein.

Returning to step S2424, if the entity instance is not configured as visible in the allocation metadata, then at step S2428 the network management virtualizer 100 discards the received operational data so that the received operational data is not dispatched to the slice owner 110-S-1 for the virtual network slice S-1 stored at the physical network datastore 1020.

Returning to step S2414, if the identified entity type is not classified as create-able, then at step S2422 the network management virtualizer 100 checks the identified entity type to determine whether the identified entity type is classified as allocate-able (belongs in the allocate-able category).

If the identified entity type is classified as allocate-able, then the process proceeds to step S2424 and continues as discussed herein.

Returning to step S2422, if the identified entity type is not classified as allocate-able, then at step S2426 the network management virtualizer 100 checks the identified entity type to determine whether the identified entity type is classified as within the notification scope for the virtual network slice S-1. The network management virtualizer 100 may determine whether the identified entity type is classified as within the notification scope for the virtual network slice S-1 in the same or substantially the same manner as discussed above with regard to step S2226 in FIG. 22.

If the identified entity instance is classified as within the notification scope for the virtual network slice S-1, then the process proceeds to step S2420 and continues as discussed above.

Returning to step S2426, if the identified entity type is not classified as within the notification scope for the virtual network slice S-1, then the process proceeds to step S2428 and continues as discussed above.

Returning to step S2412, if the network management virtualizer 100 determines that there is not a match for the entity instance in the cached mapping, then the process proceeds to step S2428 and continues as discussed above.

Returning now to step S2408, if the network management virtualizer 100 determines that there is an entity type matching the identified entity instance, then the process proceeds to step S2414 and continues as discussed herein.

Although shown in FIG. 24, steps 52410 and 52412 may be omitted. In this case, if no match is found at step S2408, then the process proceeds to step S2428 and continues as discussed above.

FIG. 25 is a flow chart illustrating a method for autonomous provisioning of operational data according to one or more example embodiments. The method shown in FIG. 25 may be performed at the network management virtualizer 100. As with the example embodiment shown in FIGS. 22-24, the steps in the method shown in FIG. 25 may be implemented using XSLT, XQuery, XPath, Document Object Model (DOM) or related technologies if the operational data are XML-encoded. Otherwise, any technology pertinent to the encoding may be used.

Referring to FIG. 25, at step S2500 the network management virtualizer 100 receives operational data from node 104-1.

At step S2502, the network management virtualizer 100 attempts to retrieve a slice view for the virtual network slice S-1 from a cache in the physical network datastore 1020. The network management virtualizer 100 may obtain the slice view using GET-CONFIG as illustrated in, for example, FIG. 5. Slice views may optionally be cached for efficiency.

If a slice view for the virtual network slice S-1 is present in the cache, then at step S2504 the network management virtualizer 100 retrieves the slice view for the virtual network slice S-1 from the cache.

At step S2506, the network management virtualizer 100 obtains a matching (e.g., XPath) query expression based on the entity instance (resource) information available in the received operational data. The expression allows for the optional presence of a prefix in the key value of the entity instance such that a matching entity instance may be found in the slice view with or without a prefix.

At step S2510, the network management virtualizer 100 executes the query against the slice view.

At step S2514, the network management virtualizer 100 checks the result of the query execution at step S2510 to determine if there is a matching entity instance in the slice view. This indicates whether the entity is visible in the slice view.

If there is not a matching entity instance in the slice view, then at step S2528 the network management virtualizer 100 discards the received operational data so that the received operational data is not dispatched to the slice owner 110-S-1 for the virtual network slice S-1 stored at the physical network datastore 1020.

Returning to step S2514, if the network management virtualizer 100 determines that there is a matching entity instance in the slice view, then at step S2516 the network management virtualizer 100 checks the key value of the entity instance from the received operational data to determine whether the entity instance is prefixed. The network management virtualizer 100 determines whether the entity instance is prefixed in the same or substantially the same manner as discussed above with regard to step S2316 in FIG. 23.

If the network entity is prefixed, then at step S2518 the network management virtualizer 100 removes the prefix from the key value in the received operational data to generate transformed operational data. The network management virtualizer 100 may remove the prefix in the same or substantially the same manner as discussed above with regard to step S2318 in FIG. 23.

At step S2520, the network management virtualizer 100 forwards the transformed operational data to be dispatched to the slice owner 110-S-1.

Returning to step S2516, if the entity instance is not prefixed, then the process proceeds to step S2520 and continues as discussed above.

Returning to step S2502, if a slice view for the virtual network slice S-1 is not present in the cache, then at step S2508 the network management virtualizer 100 obtains the slice view for the virtual network slice S-1 in the same or substantially the same manner as discussed above with regard to step S2308 in FIG. 23. Also at step S2508, the network management virtualizer 100 inserts the obtained slice view into the cache. The process then proceeds to step S2506 and continues as discussed herein.

Although discussed separately, the example embodiments shown in FIGS. 24 and 25 may be implemented in combination with one another and/or used interchangeably.

According to at least some example embodiments, network management entity instances (e.g., configurable resources that reside in the network management virtualizer or other network manager) may also be sliced. In one example, slice metadata (allocation or the like) may be partially or wholly visible to a slice owner. This metadata may be configured in the network management virtualizer, as opposed to a network device. Slice owners may be slice aware or not, either or both of which may be supported by exposing slice-related metadata or not, respectively.

Network manager entity types may be sliced in the same or substantially the same manner as entity types of network devices. Moreover, the same or substantially the same configure-ability may apply to network manager entity types and entity instances as to entity types and entity instances of network devices. Accordingly, one or more example embodiments may be applicable to any Yang-modelled entity in the scope of network managers and all device types.

According to one or more example embodiments, autonomous notifications and/or operational data may originate at the network management virtualizer and be processed for slicing in the same or substantially the same way as autonomous notifications and/or operational data from devices in the physical network. Network devices may be slice aware or not, either or both of which may be supported by example embodiments.

FIG. 26 illustrates classification metadata according to one or more example embodiments.

Referring to FIG. 26, the classification metadata shown in FIG. 26 is similar to the classification metadata shown in FIG. 15, but further includes “Entities in the notification scope of slices” entries.

The “Entities in the notification scope of slices” define the entity instances (e.g., via a list) for which autonomous notifications and operational data are visible by a slice owner. This category of explicit entity type descriptions is used to complement those in the create-able and allocate-able categories. The notification scope category enables the filtering and transformation of autonomous notifications illustrated in, for example, FIG. 22, and the filtering and transformation of operational data as illustrated in, for example, FIG. 24.

FIG. 19 depicts a high-level block diagram of a computer, computing or electronic device suitable for use in implementing, inter alia, network management virtualizer, nodes, as well as other network elements and/or devices.

Referring to FIG. 19, the computer 1900 includes one or more processors 1902 (e.g., a central processing unit (CPU) or other suitable processor(s)) and a memory 1904 (e.g., random access memory (RAM), read only memory (ROM), and the like). The computer 1900 also may include a cooperating module/process 1905. The cooperating process 1905 may be loaded into memory 1904 and executed by the processor 1902 to implement functions as discussed herein and, thus, cooperating process 1905 (including associated data structures) may be stored on a computer readable storage medium (e.g., RAM memory, magnetic or optical drive or diskette, or the like).

The computer 1000 also may include one or more input/output devices 1906 (e.g., a user input device (such as a keyboard, a keypad, a mouse, and the like), a user output device (such as a display, a speaker, and the like), an input port, an output port, a receiver, a transmitter, one or more storage devices (e.g., a tape drive, a floppy drive, a hard disk drive, a compact disk drive, and the like), or the like, as well as various combinations thereof).

Although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of this disclosure. As used herein, the term “and/or,” includes any and all combinations of one or more of the associated listed items.

When an element is referred to as being “connected,” or “coupled,” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. By contrast, when an element is referred to as being “directly connected,” or “directly coupled,” to another element, there are no intervening elements present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., “between,” versus “directly between,” “adjacent,” versus “directly adjacent,” etc.).

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms “a,” “an,” and “the,” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes,” and/or “including,” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be noted that in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may in fact be executed substantially concurrently or may sometimes be executed in the reverse order, depending upon the functionality/acts involved.

Specific details are provided in the following description to provide a thorough understanding of example embodiments. However, it will be understood by one of ordinary skill in the art that example embodiments may be practiced without these specific details. For example, systems may be shown in block diagrams so as not to obscure the example embodiments in unnecessary detail. In other instances, well-known processes, structures and techniques may be shown without unnecessary detail in order to avoid obscuring example embodiments.

As discussed herein, illustrative embodiments will be described with reference to acts and symbolic representations of operations (e.g., in the form of flow charts, flow diagrams, data flow diagrams, structure diagrams, block diagrams, etc.) that may be implemented as program modules or functional processes include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types and may be implemented using existing hardware at, for example, existing CPE devices, Distribution Point Units (DPUs), network management virtualizers, network management entities, clients, gateways, nodes, agents, controllers, computers, cloud based servers, web servers, proxies or proxy servers, application servers, load balancers or load balancing servers, heartbeat monitors, device management servers, or the like. As discussed later, such existing hardware may include, inter alia, one or more Central Processing Units (CPUs), system-on-chip (SOC) devices, digital signal processors (DSPs), application-specific-integrated-circuits, field programmable gate arrays (FPGAs) computers or the like.

Although a flow chart may describe the operations as a sequential process, many of the operations may be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. A process may be terminated when its operations are completed, but may also have additional steps not included in the figure. A process may correspond to a method, function, procedure, subroutine, subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or the main function.

As disclosed herein, the term “storage medium”, “computer readable storage medium” or “non-transitory computer readable storage medium” may represent one or more devices for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and/or other tangible machine readable mediums for storing information. The term “computer-readable medium” may include, but is not limited to, portable or fixed storage devices, optical storage devices, and various other mediums capable of storing, containing or carrying instruction(s) and/or data.

Furthermore, example embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks may be stored in a machine or computer readable medium such as a computer readable storage medium. When implemented in software, a processor or processors will perform the necessary tasks.

A code segment may represent a procedure, function, subprogram, program, routine, subroutine, module, software package, class, or any combination of instructions, data structures or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

The terms “including” and/or “having”, as used herein, are defined as comprising (i.e., open language). The term “coupled”, as used herein, is defined as connected, although not necessarily directly, and not necessarily mechanically. Terminology derived from the word “indicating” (e.g., “indicates” and “indication”) is intended to encompass all the various techniques available for communicating or referencing the object/information being indicated. Some, but not all, examples of techniques available for communicating or referencing the object/information being indicated include the conveyance of the object/information being indicated, the conveyance of an identifier of the object/information being indicated, the conveyance of information used to generate the object/information being indicated, the conveyance of some part or portion of the object/information being indicated, the conveyance of some derivation of the object/information being indicated, and the conveyance of some symbol representing the object/information being indicated.

According to example embodiments, CPE devices, endpoints, DPUs, network management virtualizers, network management entities, clients, gateways, nodes, agents controllers, computers, cloud based servers, web servers, application servers, proxies or proxy servers, load balancers or load balancing servers, heartbeat monitors, device management servers, or the like, may be (or include) hardware, firmware, hardware executing software or any combination thereof. Such hardware may include one or more Central Processing Units (CPUs), system-on-chip (SOC) devices, digital signal processors (DSPs), application-specific-integrated-circuits (ASICs), field programmable gate arrays (FPGAs) computers or the like configured as special purpose machines to perform the functions described herein as well as any other well-known functions of these elements. In at least some cases, CPUs, SOCs, DSPs, ASICs and FPGAs may generally be referred to as processing circuits, processors and/or microprocessors.

The CPE devices, endpoints, DPUs, network management virtualizers, network management entities, clients, gateways, nodes, agents, controllers, computers, cloud based servers, web servers, application servers, proxies or proxy servers, load balancers or load balancing servers, heartbeat monitors, device management servers, or the like, may also include various interfaces including one or more transmitters/receivers connected to one or more antennas, a computer readable medium, and (optionally) a display device. The one or more interfaces may be configured to transmit/receive (wireline and/or wirelessly) data or control signals via respective data and control planes or interfaces to/from one or more network elements, such as switches, gateways, termination nodes, controllers, servers, clients, and the like.

Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments of the invention. However, the benefits, advantages, solutions to problems, and any element(s) that may cause or result in such benefits, advantages, or solutions, or cause such benefits, advantages, or solutions to become more pronounced are not to be construed as a critical, required, or essential feature or element of any or all the claims.

Reference is made in detail to embodiments, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. In this regard, the example embodiments may have different forms and should not be construed as being limited to the descriptions set forth herein. Accordingly, the example embodiments are merely described below, by referring to the figures, to explain example embodiments of the present description. Aspects of various embodiments are specified in the claims. 

What is claimed is:
 1. A method for managing a physical network, the method comprising: receiving a network information message from the physical network, the network information message including at least one of (i) an autonomous notification from a network node in the physical network or (ii) operational data for the network node in the physical network; determining whether a slice owner of a virtual network slice in the physical network is allowed to view the network information message based on at least one of classification metadata or allocation metadata associated with the virtual network slice; and providing the network information message to the slice owner in response to determining that the slice owner is allowed to view the network information message, wherein the determining whether a slice owner of a virtual network lice in the physical network is allowed to view the network information message comprises: identifying an entity instance, at the network node, that originated the network information message; and determining whether the slice owner is allowed to view the network information message based on the identified entity instance.
 2. The method of claim 1, wherein the determining whether a slice owner is allowed to view the network information based on the identified entity instance comprises: identifying an entry for an entity type in the classification metadata based on the identified entity instance; and determining whether the slice owner is allowed to view the network information message based on the entry for an entity type in the classification metadata.
 3. The method of claim 2, wherein the identifying an entry identifies the entry for an entity type in the classification metadata by matching schema details for the entity type with schema information for the entity instance.
 4. The method of claim 2, wherein the network information message includes a key value; and the determining whether the slice owner is allowed to view the network information message includes determining whether the entity type is classified as create-able for the virtual network slice in the classification metadata, determining whether the key value is prefixed with a prefix associated with the virtual network slice, and determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as create-able for the virtual network slice and whether the key value is prefixed with the prefix associated with the virtual network slice.
 5. The method of claim 2, wherein the determining whether the slice owner is allowed to view the network information message comprises: determining whether the entity type is classified as allocate-able for the virtual network slice based on the entry for an entity type in the classification metadata; determining whether the entity instance is designated as visible in the virtual network slice based on the entry for an entity type in the classification metadata; and determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as allocate-able for the virtual network slice and whether the entity instance is designated as visible in the virtual network slice.
 6. The method of claim 2, wherein the determining whether the slice owner is allowed to view the network information message comprises: determining whether the entity type is classified as within a notification scope of the virtual network slice based on the entry for an entity type in the classification metadata; and determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as within the notification scope of the virtual network slice.
 7. The method of claim 2, wherein the identifying an entry for an entry for an entity type in the classification metadata based on the entity instance comprises: querying a mapping between entity instances and entries in the classification metadata to identify the entry for an entity type in the classification metadata.
 8. A non-transitory computer readable storage medium storing computer executable instructions that, when executed at a network element, cause the network element to perform a method for managing a physical network, the method comprising: receiving a network information message from the physical network, the network information message including at least one of (i) an autonomous notification from a network node in the physical network or (ii) operational data for the network node in the physical network; determining whether a slice owner of a virtual network slice in the physical network is allowed to view the network information message based on at least one of classification metadata or allocation metadata associated with the virtual network slice; and providing the network information message to the slice owner in response to determining that the slice owner is allowed to view the network information message, wherein the determining whether a slice owner of a virtual network slice in the physical network is allowed to view the network information message comprises: identifying an entity instance at the network node having originated the network information message; determining whether the slice owner is allowed to view the network information message based on the identified entity instance.
 9. The non-transitory computer readable storage medium of claim 8, wherein the determining whether the slice owner is allowed to view the network information message based on the identified entity instance comprises: identifying an entry for an entity type in the classification metadata based on the identified entity instance; and determining whether the slice owner is allowed to view the network information message based on the entry for an entity type in the classification metadata.
 10. The non-transitory computer readable storage medium of claim 9, wherein the identifying an entry identifies the entry for an entity type in the classification metadata by matching schema details for the entity type with schema information for the entity instance.
 11. The non-transitory computer readable storage medium of claim 9, wherein the network information message includes a key value; and the determining whether the slice owner is allowed to view the network information message includes determining whether the entity type is classified as create-able for the virtual network slice in the classification metadata, determining whether the key value is prefixed with a prefix associated with the virtual network slice, and determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as create-able for the virtual network slice and whether the key value is prefixed with the prefix associated with the virtual network slice.
 12. The non-transitory computer readable storage medium of claim 9, wherein the determining whether the slice owner is allowed to view the network information message comprises: determining whether the entity type is classified as allocate-able for the virtual network slice based on the entry for an entity type in the classification metadata; determining whether the network entity is designated as visible in the virtual network slice based on the entry for an entity type in the classification metadata; and determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as allocate-able for the virtual network slice and whether the entity instance is designated as visible in the virtual network slice.
 13. The non-transitory computer readable storage medium of claim 9, wherein the determining whether the slice owner is allowed to view the network information message comprises: determining whether the entity type is classified as within a notification scope of the virtual network slice based on the entry for an entity type in the classification metadata; and determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as within the notification scope of the virtual network slice.
 14. The non-transitory computer readable storage medium of claim 9, wherein the identifying an entry for an entity type in the classification metadata based on the entity instance comprises: querying a mapping between network entities and entries in the classification metadata to identify the entry for an entity type in the classification metadata.
 15. A network element to manage a physical network, the network element comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the network element to receive a network information message from the physical network, the network information message including at least one of (i) an autonomous notification from a network node in the physical network or (ii) operational data for the network node in the physical network, determine whether a slice owner of a virtual network slice in the physical network is allowed to view the network information message based on at least one of classification metadata or allocation metadata associated with the virtual network slice, and provide the network information message to the slice owner in response to determining that the slice owner is allowed to view the network information message, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the network element to determine whether the slice owner of the virtual network slice in the physical network is allowed to view the network information message by identifying an entity instance at the network node having originated the network information message, and determining whether the slice owner is allowed to view the network information message based on the identified entity instance.
 16. The network element of claim 15, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the network element to determine whether the slice owner is allowed to view the network information message based on the identified entity instance by identifying an entry for an entity type in the classification metadata based on the entity instance; and determining whether the slice owner is allowed to view the network information message based on the entry for an entity type in the classification metadata.
 17. The network element of claim 16, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the network element to identify the entry for the entity type in the classification metadata by matching schema details for the entity type with schema information for the entity instance.
 18. The network element of claim 16, wherein the network information message includes a key value; and the at least one memory and the computer program code are further configured to, with the at least one processor, cause the network element to determine whether the slice owner is allowed to view the network information message by determining whether the entity type is classified as create-able for the virtual network slice in the classification metadata, determining whether the key value is prefixed with a prefix associated with the virtual network slice, and determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as create-able for the virtual network slice and whether the key value is prefixed with the prefix associated with the virtual network slice.
 19. The network element of claim 16, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the network element to determine whether the slice owner is allowed to view the network information message by determining whether the entity type is classified as allocate-able for the virtual network slice based on the entry for an entity type in the classification metadata; determining whether the entity instance is designated as visible in the virtual network slice based on the entry for an entity type in the classification metadata; and determining whether the slice owner is allowed to view the network information message based on whether the entity type is classified as allocate-able for the virtual network slice and whether the entity instance is designated as visible in the virtual network slice.
 20. The network element of claim 16, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the network element to identify the entry for an entity type in the classification metadata based on the entity instance by querying a mapping between entity instance and entries in the classification metadata to identify the entry for an entity type in the classification metadata. 